It probably would have helped enormously if they had given it a professional name other than "toast".
Toast is the official ux name for a popup notification.
Introducing a new HTML element – welcome
171–180 of 234 posts
Re: Introducing a new HTML element – welcome <clippy>
#172Earlier quoted context omitted.
I try switching from Chrome to Firefox at least once a year, but the UI design keeps me firmly entrenched as a Chrome user.
I used to use Firefox but it blew chunks at doing intranet authentication. Auth prompts for days. I had to use an extension that loaded an IE browser pane so that I wouldn’t spend half my work day typing my password. I hope they have improved.
This is and isn't an issue.
By default, intranet authentication (spnego) is disabled in Firefox. There are numerous guides explaining how to turn it on, and it takes all of a couple of minutes to set up correctly after which point it just works.
FWIW IE has this problem too, in that by default it only enables negotiation for unqualified hostnames. If you want people to use an FQDN, you have to go add that FQDN to a list buried behind a couple of advanced dialogs.
Re: Introducing a new HTML element – welcome <clippy>
#173Earlier quoted context omitted.
No, IE6 was far less terrible than IE4, but still amazingly awful. If was from the era of browsers where you had to essentially code up different copies of a page per-browser if you wanted any sort of graphical anything.
No you didn't. You had to code exactly one copy: for IE6. Nobody cared about anything else. Just like nowadays more and more pages only get coded for chrome and might or might not work on Firefox.
Except that IE6 didn't die when IE7 came out - it stuck around. I was working at a company that still had to support IE6 when IE8 was coming out - and firefox was quite popular by that point - we ended up dropping support for it shortly after chrome got popular.
IE6 outlived it's expected lifetime by leaps and bounds due to lots of customers stuck on machines locked into running old version of windows due to financial or corporate policy reasons.
Re: Introducing a new HTML element – welcome <clippy>
#174The person writing this has to repeat frequently that they're OK with the element; it's quite funny how hard they try not to upset people. But their view of the situation is completely correct; just because this one feature might be useful (heck, when Microsoft dumped XMLHttpRequest on us that was incredible too), doesn't change the fact that we're now living in a web where Google does whatever it wants, adds whateve…
There's a difference between now and the 90s/00s. And its worse now. At least Microsoft's overarching goal was just to get developers to use their platform, by making their platform as useful as possible (even if many of the changes were ultimately misguided). With Google, there's some of this, but there's also some very clear "we're an ads company and we want the ad experience on Chrome to favor us as much as possib…
I would say that anyone who has spent an extensive amount of time writing code that needed to work with IE6 or below would disagree with your statement.
Re: Introducing a new HTML element – welcome <clippy>
#175Earlier quoted context omitted.
Not the OP, but I'll chip in with my $.02. I really want to like Firefox, but everything UI feels wrong (on macOS). From tabs, where the close button is on the wrong side (right) and if you click the + button to open a new tab the cursor ends up over the new tab, not over the + button so you can click again to open a new tab. The whole UI looks and feels non-native. Pressing ESC in full screen mode does not bring the…
> and if you click the + button to open a new tab the cursor ends up over the new tab, not over the + button so you can click again to open a new tab. Same experience for me on Chrome on macOS too, so... You sure you didn't change those defaults somehow? I usually open new tabs with Command + t or Control + t on Linux / Windows.
[deleted]
Re: Introducing a new HTML element – welcome <clippy>
#176> I think the chaps at Google probably think they're the good guys. That they're doing the web a favour. That users love them.
This. Apple is in this self-reflecting bubble too. Companies that start off user-focused and get big often become thoroughly narcissistic.
Re: Introducing a new HTML element – welcome <clippy>
#177From the chromium forum: "Intent to Implement: Toast UI element" https://groups.google.com/a/chromium.org/forum/m/#!msg/blink...
>Firefox: No public signals >Edge: No public signals >Safari: No public signals >Web developers: Positive (previously expressed privately; we've encouraged them to make their interest public on the WICG thread) So basically, nobody at Google talked to anyone about this, asked only google engineers and then pushed those mentioned google engineers to make postive comments in the standards thread? And none of the other…
One engineer shared the idea yesterday [1] of introducing a new element in Chrome behind an experiment flag to play with and you are mortified that Mozilla, Microsoft and Apple haven't responded with an official position within 24h?
[1] https://groups.google.com/a/chromium.org/forum/m/#!msg/blink...
Re: Introducing a new HTML element – welcome <clippy>
#178Earlier quoted context omitted.
I don't really agree with the "Chrome is the new IE" sentiment. They participate in the Web Standards process the same as anyone else. That their voice has different gravity in the process due to the fact that they are often the ones pushing the standards forward isn't something they should be compared to IE for. Devs old enough to recall the halcyon days of IE know it was quite different...
With Chrome, you also get Chromium, and the ability to see inside(and contribute!) to development. This did not exist in the IE-dominated era. Link to chromium dev: https://www.chromium.org/getting-involved/dev-channel
I'm not going to give any assistance at all to Google, and I'd caution others to think carefully before doing so.
Re: Introducing a new HTML element – welcome <clippy>
#179Thought was about IoT light kitchen appliances. Turns out it's about asking will a person accept cookies. element plus a $30 home speaker is the intended norm, except "Clippy" is now powered by the cloud, and our favorite foods have become digital identifiers.
Re: Introducing a new HTML element – welcome <clippy>
#180Earlier quoted context omitted.
> since when does actual real-life toast smoothly rise and fall again? Perhaps the inspiration came from the Sunbeam Radiant Control toaster: https://youtu.be/1OfxlSG6q5Y Unlike modern toasters which rudely attempt to catapult your toast into orbit, the Sunbeam gracefully and almost silently presents your toast with the love and care it deserves.
OK, getting off topic, but: we had this toaster when I was a kid, and I hated everything about it. This is the worst toaster I ever used. Getting it to engage was super finicky. I never saw anybody get it to work on the first try. You often had to whack it down pretty hard to make it work, while other times a light touch was sufficient. You could tell when someone was using it from across the house because you heard…
> You could tell when someone was using it from across the house because you heard a metallic "whang, whang, whang, whang!", at various volumes, as they tried to get it to trigger.
Lolol....reminds me of our first family toaster from the 70's.
But my dreams of owning one of these are now shattered :)