{"id":292113,"date":"2019-07-02T15:40:51","date_gmt":"2019-07-02T22:40:51","guid":{"rendered":"http:\/\/css-tricks.com\/?p=292113"},"modified":"2019-07-02T15:40:51","modified_gmt":"2019-07-02T22:40:51","slug":"toast","status":"publish","type":"post","link":"https:\/\/css-tricks.com\/toast\/","title":{"rendered":"Toast"},"content":{"rendered":"
One day, all the sudden, I started hearing jokes about toast. I had no idea what the context was. I assumed some friends just got started telling toast jokes, which isn’t rare by any means. But it turns out it was a whole thing<\/em>. It got me thinking, jeez, if I can’t keep up with this stuff when it’s kinda my job, it must be extra<\/em> tough for people who actually do work for a living. <\/p>\n Anyway. Thankfully Jeremy summed it up nicely:<\/p>\n First off, this all kicked off with the announcement of \u201cintent to implement\u201d<\/a>. That makes it sounds like Google are intending to, well, \u2026implement<\/em> this. In fact \u201cintent to implement\u201d really means \u201cintend to mess around with this behind a flag\u201d. The language is definitely confusing and this is something that will hopefully be addressed<\/a>.<\/p>\n Secondly, Chrome isn\u2019t going to ship a <\/p>\n The drama around it, hence the cause of all the jokes and such, was the fact that it felt like it came out of nowhere and was Chrome strongarming a feature through the standards process, or perhaps kinda skipping that process. Terence’s humorous post<\/a> digs into that a bit more. <\/p>\n I’m not sure if Google is actually doing anything nefarious here. It’s behind a flag, so I guess the point of that is to explore and research and stuff. Feels very similar to kv:storage<\/a> to me, a “native module” much like a “native custom element.”<\/p>\n But we should be extra watchful<\/em> about stuff like this. If any browser goes rogue and just starts shipping stuff, web standards is over. Life for devs gets a lot harder and the web gets a lot worse. The stakes are high. And it’s not going to happen overnight, it’s going to happen with little tiny things like this. Keep that blue beanie on.<\/p>\n Regarding the element itself, it’s always a bit surprising to me to see what gets legs as far as new HTML elements. Toasts just seem like a positioned \n See the Pen I would have guessed something like dropdown menus or tabs would have been the strongest contenders for “native” web components. <\/p>\n","protected":false},"excerpt":{"rendered":" One day, all the sudden, I started hearing jokes about toast. I had no idea what the context was. I assumed some friends just got started telling toast jokes, which isn’t rare by any means. But it turns out it was a whole thing. It got me thinking, jeez, if I can’t keep up with […]<\/p>\n","protected":false},"author":3,"featured_media":292320,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_bbp_topic_count":0,"_bbp_reply_count":0,"_bbp_total_topic_count":0,"_bbp_total_reply_count":0,"_bbp_voice_count":0,"_bbp_anonymous_reply_count":0,"_bbp_topic_count_hidden":0,"_bbp_reply_count_hidden":0,"_bbp_forum_subforum_count":0,"sig_custom_text":"","sig_image_type":"featured-image","sig_custom_image":0,"sig_is_disabled":false,"inline_featured_image":false,"c2c_always_allow_admin_comments":false,"footnotes":"","jetpack_publicize_message":"","jetpack_is_tweetstorm":false,"jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":[]},"categories":[4],"tags":[1536],"jetpack_publicize_connections":[],"acf":[],"jetpack_featured_media_url":"https:\/\/i0.wp.com\/css-tricks.com\/wp-content\/uploads\/2019\/07\/toast.png?fit=1200%2C600&ssl=1","jetpack-related-posts":[{"id":210238,"url":"https:\/\/css-tricks.com\/redesigning-the-toast\/","url_meta":{"origin":292113,"position":0},"title":"Redesigning The Toast","date":"October 28, 2015","format":false,"excerpt":"Karen McGrane tweets, dreamteam assembles, epic redesign ensues, story of entire process published. Some minor nuggets #RelevantToMyInterets: A big part of the effort was content strategy and taxonomy work. Cleaning up the tag and category system (and actually inventing different types of tags) meant they could offer many more interesting\u2026","rel":"","context":"In "Link"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":351389,"url":"https:\/\/css-tricks.com\/dont-attach-tooltips-to-document-body\/","url_meta":{"origin":292113,"position":1},"title":"Don\u2019t attach tooltips to document.body","date":"September 8, 2021","format":false,"excerpt":"Here's Atif Afzal on using a \n
toast<\/code> element. Instead, this is a proposal for a custom element<\/a> currently called
std-toast<\/code>. I\u2019m assuming that should the experiment prove successful, it\u2019s not a foregone conclusion that the final element name will be called
toast<\/code>.<\/p>\n<\/blockquote>\n
<dialog><\/code> to me, but I haven’t participated in any research or anything. They are popular enough for Bootstrap to have ’em<\/a>:<\/p>\n
\n Bootstrap Toasts<\/a> by Chris Coyier (@chriscoyier<\/a>)
\n on CodePen<\/a>.<\/span>\n<\/p>\n