You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey, @wesbos, thank you for bringing this up. This feature was disabled on purpose for several reasons:
This feature doesn’t work as expected with users who use different keyboard layouts. So, for example, with this feature, I could create a URL like /keycode/for/ū, then copy and share it with someone who doesn’t use a Latvian keyboard or layout. This will result in a blank page unless we hardcode this letter and its info as well. We created the ability to share permalinks to the items from the table - it’s extensive but doesn’t cover all available variants for all available keys and codes (and is already not 100% correct for everyone). The way it was originally implemented is also not ideal if you would for example type an ä character and then reload the page - all the info will be missing
Another reason is SEO. It’s important to have identical content for a single URL at all times. And with that feature, the result would vary from os to os unless we hardcode every possible keycode which is also not possible due to the way the keycode detection works (a lot of variance for the same keys and codes between different layouts).
With this said, we decided to let this feature go until further improvement is agreed upon. For now, we decided to let the only permalinks be the keys in the table.
We have an idea for generating permalinks in the spirit of whatsmybrowser snapshots, taking into account all the data from the current user including the layout, but this will require some significant changes.
On th version of the site before your updates, the URL would change as you type.
/for/y
for/for/y
The URLs still work, but the urls are not changing as you type: https://www.toptal.com/developers/keycode/y
The text was updated successfully, but these errors were encountered: