Yup, that actually is perfectly expected behaviour.
First I think you’ve got to understand what that search you’re doing is actually looking for and returning back to you. The search bar on openstreetmap.org uses an OSM-specific search engine called Nominatim, and all it’s really looking through is “raw” data that has been entered on OSM. Think of the openstreetmap.org website not so much as a map, but a user interface to see data that has been entered into a database. When you search for, for example, “McRae Street, Okotoks” Nominatim just spits out the line segments that happen to have “McRae Street” entered into a “name” data point associated with them. It’s not giving you “McRae Street” in its entirety.
So, similarly, when you look for the postal code “T1S 1J5” Nominatim just extrapolates a centre point that averages the position of everything in the database that happens to have the “addr:postalcode=T1S 1J5” data point entered into it. Nominatim can highlight road segments with the name “McRae Street”; unfortunately it can’t highlight every house in the database with the T1S 1J5 postal code.
When you go looking at other online maps that can seemingly highlight where the postal code “is”, those maps are just extrapolating an “area” over which the postal code applies. However, that’s not how it’s actually defined by Canada Post. Canada Post has a (proprietary) database of postal codes and associated addresses, and vice versa, but it’s not really something that is geographically defined. For example you can extrapolate that T1S 1J5 is geographically associated with McRae Street east of Poplar Avenue, in the town of Okotoks, Alberta, but Canada Post just randomly assigned it that way. There’s nothing stopping that code from being reassigned somewhere else, and it’s not really entirely consistent either: there’s a house further north on Poplar Avenue with the T1S 1J5 postal code too, but there’s a townhouse development between that has an entirely different postal code, T1S 1Z5. Similarly the apartment building at the southeast corner of McRae and Poplar has its own unique postal code, T1S 2H4; literally no other building in the country uses that postal code.
As such, because the postal codes are only tangentially related to the addresses of buildings, there aren’t specific boundaries in the OSM database that define where one postal code ends and another begins, and the functionality you’d like Nominatim to have just isn’t there.
Now, you might argue “well why don’t we just map those boundaries in OSM?” I for one personally don’t think it’s a good idea because:
- the aforementioned fact that they’re not technically defined by their geographic location,
- there are many parcels of land that don’t have an associated postal code, so technically a “postal code map” if done “correctly” will have lots of gaps and discontinuities that overzealous people are going to try to erroneously extrapolate,
- conversely there are many postal codes which don’t have an associated physical location, i.e. P.O. boxes
- big buildings (think skyscrapers in Downtown Calgary) sometimes have multiple, overlapping postal codes