I've just given it a quick go and gone straight back to v3. Fusion on Lion still lacks native full screen and the interface feels a lot slower. Nevermind, maybe a rush to compete with Parallels?
Although one major disadvantage I've discovered recently is that if you embed an iframe (with a no-cache response header, i.e. Facebook's like button) it stops Firefox adding the page to the back-forward cache. Same with Webkit if the protocols don't match. https://developer.mozilla.org/en/using_firefox_1.5_caching
I wonder how much extra bandwidth Facebook has wasted worldwide by doing this? Twitter allows caching for 30 mins at least, good enough for back/forward caching to be useful.
Looks fantastic, but here's another feature it doesn't have which makes it feel less native.
Try mouse scrolling too far whilst the menu's options are open/visible. The parent page scrolls as well when you reach the start/end. This doesn't happen with a normal select menu.
I wonder if there's a way to do an event.preventDefault() on the mouse scroll event when reaching the end of the list?
Not just looks, it solves certain big usability problems I have with regular selects or checkboxes for values. However the few non-native problems are indeed problematic. We got brainpower here, lets make it work!
Yep, I swapped it out at the last second. The previous typeface allowed embedding without OTF and TTF. Someone raised the issue over Twitter and it is now being tracked on GitHub.
Has anyone got any research on how this can affect users?
I recently persuaded a developer to not use it. It was quite frustrating during testing to see the 'mask' (made from underscores and slashes) expand and contract when they're typed over with non fixed-width characters of differing sizes.
I'd much rather see three small input fields for a date (with some Javascript input filtering) than a field with some underscores and slashes inserted dynamically.
https://github.com/nodejs/node/releases/tag/v12.17.0