31–40 of 144 posts
I looked at the source, looks neat except one thing: shouldn't there be double quotes around all href targets? The ones that have a single quote (e.g. What's Inside All the iPhones ) get marked in red in firefox's view source due to this
Only the ones that need it. Like for example when there is a single quote in the link like you mentioned.
I looked at the source, looks neat except one thing: shouldn't there be double quotes around all href targets? The ones that have a single quote (e.g. What's Inside All the iPhones ) get marked in red in firefox's view source due to this
Earlier quoted context omitted.
It seems to me, many web developers today don't even realize, that creating features without js and enriching the experience from that baseline, not only enhances performance and accessibility, but in the end is often not more work and might even lead to cleaner, leaner code. I guess in the end it just comes down to which tools one learned first and based on that which approach one takes to solve the problem at hand.…
css is often the slowest part of a webapp. complex css like this is not necessarily better accessibility-wise than javascipt
Of course, small hover menus offer their own accessibility challenges, but they don't depend on the way they are implemented but rather the choice of UX. And no reason why you could not improve this simple css menu with some js to make it more user friendly (like turning hover into clicks etc.)
Awful usability. I expect that when hovering over a section and moving my cursor to the right I would stay within that section, but it always just reverts to home or whatever other section I've clicked. If hovering over a section doesn't enable access to that section, then don't show the expanded version. Wait for a click event to show it at all.
That's not the actual Bloomberg[0] menu. This copy does not seem to implement that feature, which is one of the most important features to have I think. [0] http://www.bloomberg.com/
It took VLC ages to get rid of this issue, but it is solved as of VLC 3.0.3 (relevant Qt bug: [2]).
Off topic but that is a gnarly commit history
Earlier quoted context omitted.
There's a good article about Amazon implementing this feature for their mega menu. Blew me away when I first read it, it's very obvious and simple in hindsight. http://bjk5.com/post/44698559168/breaking-down-amazons-mega-...
Yes, there are some great tips. I still think this style menu is just bad, though. Although certain tweaks can improve the UX, it's still an frustratingly unusable interface for people with certain motor disabilities and even just older users whose mouse/trackpad skills are not great.
Pretty cool indeed! Found a bug with Chrome 67.0.3396.87 on Mac OS 10.11.6: When you hover over a menu item (e.g. "Markets"), the sub-menu updates based on the sub-items for the "Markets" item. However, when moving the cursor right (towards the sub-menu), the sub-menu state reverts back to the last activated menu item. Only clicking a menu item makes the respective sub-menu "stick". This is not the case for the actua…
Earlier quoted context omitted.
It seems to me, many web developers today don't even realize, that creating features without js and enriching the experience from that baseline, not only enhances performance and accessibility, but in the end is often not more work and might even lead to cleaner, leaner code. I guess in the end it just comes down to which tools one learned first and based on that which approach one takes to solve the problem at hand.…
css is often the slowest part of a webapp. complex css like this is not necessarily better accessibility-wise than javascipt
Try clicking on the "Markets > Read: Economics" link.