Toast

Recently, the web development community erupted in a flurry of toast-related jokes. The reason? A seemingly sudden proposal for a native "toast" element in Chrome. This caught many off guard, highlighting the challenges developers face in keeping up with rapid changes in web technologies.

Jeremy's insightful summary clarifies the situation:

The initial announcement, using the phrase "intent to implement," was misleading. It implied a direct implementation, when in reality, it's an experimental feature behind a flag. This ambiguous language needs improvement. Crucially, Chrome isn't adding a built-in <toast></toast> element; it's proposing a custom element, tentatively named std-toast. Even if successful, the final name might differ.

The controversy stems from the perceived abruptness of the proposal and concerns that Chrome might be bypassing the standard web development process. Terence's humorous take delves deeper into this aspect.

While Google's intentions might not be malicious—the experimental nature, hidden behind a flag, suggests research and exploration—it's a situation demanding vigilance. Unilateral browser implementations threaten web standards, increasing development complexity and negatively impacting the web experience. This isn't a sudden cataclysm, but a gradual erosion through seemingly minor changes.

The choice of "toast" as a candidate element is also noteworthy. It appears functionally similar to a positioned <dialog></dialog> element, though further research is needed. Its popularity is evident in frameworks like Bootstrap, which already include toast functionality.

I personally would have anticipated elements like dropdown menus or tabs to be prioritized for native web component status.

The above is the detailed content of Toast. For more information, please follow other related articles on the PHP Chinese website!