231–234 of 234 posts
Earlier quoted context omitted.
> Devs old enough to recall the halcyon days of IE know it was quite different... I'm old enough. People sharing your view, are agreeing with a broad assumption that isn't based in reality. Ironically, the Chrome has had to adopt from the other direction (webasm) and hasn't created much whole-cloth that other browsers have had to adopt...and developer's certainly aren't hambstringed by these small additions that make…
It's not just developers, just like Microsoft made web applications that only worked on IE (think Outlook.com and the introduction of AJAX) we've seen it here on HN all the time, they announce new products that are only known to work on Chrome initially. Some have even changed the user agent and it works on Firefox, so there's some old school Embrace Extend Extinguish nonsense going on from Google's end when they int…
Can you show any examples of these "features" that are forcing the hand of other browsers?
> think Outlook.com and the introduction of AJAX
https://www.sitepoint.com/xmlhttprequest-vs-the-fetch-api-wh...
I remember that every browser had an AJAX API, where IE had a specific API that was more straightforward. The AJAX capability was a forgone conclusion rather than a technical leapfrog. You could always had access to an HTML request and timers to code AJAX as a final backup.
Unlike the author, I do not think is a good idea. Elements are supposed to express semantics, but this just suggests behaviour. Not very descriptive behaviour either - since when does actual real-life toast smoothly rise and fall again? Possibly from the ceiling or coming in from the side? Why not just call it ? Or even better, don’t add anything - it’s surely just a that needs styling and animating with existing CSS…
The name is the least concern here. But it's called a toast because that's what many UX people have called it for years, because it pops up and toast pops up. It's a specific kind of notification, not any notification. (There's also "butter bar" and "modal dialog" and so on.) And yes it's behavior, but and and and define plenty of behavior too. I think the big concern here is standards and process... not its name or…
Thanks for this, it hadn’t occurred to me why they chose this name
Earlier quoted context omitted.
The search bar in Firefox always assumes you're attempting to visit a URL if you type two words separated by a dot. It's incredibly frustrating trying to search things like "table.sort" and being redirected to a URL that doesn't resolve to anything and will almost certainly not for a while. Chrome doesn't have the same behavior (it ships with a list of valid TLDs). I get that you can work around it easily by typing a…
> "table.sort" Just curious, are you developing in Lua? That would be my guess from that string.