Interop 2024 mid-year update | Blog | web.dev
Interop 2024 mid-year update Stay organized with collections Save and categorize content based on your preferences. As we head into the second half of the year, it's a great time to look at how Interop 2024 has improved web interoperability this year. Where we started At the beginning of the year, Chrome had an experimental browser support score of 83. Today that score is 90, with a score for stab
Be the browser’s mentor, not its micromanager. - Build Excellent Websites
Give the browser some solid rules and hints, then let it make the right decisions for the people that visit it, based on their device, connection quality and capabilities. This is how they will get a genuinely great user experience, rather than a fragmented, broken one. This website was the focal point of a talk, Andy Bell—the founder of Set Studio—did in 2022. You can watch him deliver it as a cl
Open Web Advocacy
We are a group of software engineers from all over the world who have come together to advocate for the future of the open web by providing regulators, legislators and policy makers the intricate technical details that they need to understand the major anti-competitive issues in our industry and how to solve them. The entire future of Application Development is at stake. Without regulatory or legi
On browser compatibility and support baselines · molily
Preface on asynchrony One of the defining features of the web is technical asynchrony. Web standards, web clients – like browsers – and web pages are never fully aligned in time. They meet sometimes but most of the time one is ahead or lags behind. Web standards are usually ahead of browsers and websites. They are designed, then browsers start implementing them. Once a web standard is stable, the
Baseline's evolution on MDN | MDN Blog
Today we're updating the Baseline widget and rolling it out for more pages to align with the refined Baseline definition and help developers understand the status of web platform features better. First introduced in May 2023, Baseline offered a new way of looking at the state of the web platform. It established a common measure for new features coming to the web and existing ones. The idea was sim
AI時代のWebブラウザから考えるWebアクセシビリティの本質 ――Vivaldiのアプローチから | gihyo.jp
2023年5月、Vivaldiの日本先行でのiOS版プレビューリリース発表のためヨンが来日したことをきっかけに、インターネットの将来やアクセシビリティについて語る対談の機会が設けられました。 Vivaldiブラウザの創業者ヨン・フォン・テッツナーは、'90年代から長きにわたりWebブラウザ開発に携わってきた、ブラウザ業界のキーパーソンの一人です。彼のブラウザ開発のコアには、ユーザ一人ひとりのニーズに合わせた非常に柔軟なカスタマイズ性や、プライバシー保護があります。また、一部ビックテック企業によるユーザ行動の監視から逃れ、インターネットの安全性を高めるためのオープン標準規格やルール作りなどに貢献する活動も行っています。 聞き手は、ミツエーリンクス社でWeb標準技術の策定やアクセシビリティの啓発に携わってきた木達一仁氏です。 左から木達氏、ヨン、冨田 2023年のホットトピックから～生成系AI
Interop 2023: Pushing interoperability forward
Feb 1, 2023 by Jon Davis, Tim Nguyen and Jen Simmons A year ago, Apple, Bocoup, Google, Igalia, Microsoft, and Mozilla came together to improve the interoperability of the web and to continue our commitments to web standards — actions that ensure the web will work in any browser, on any operating system, with any computer. Throughout last year, Interop 2022 focused on fifteen key areas of most imp
Introducing Baseline | Blog | web.dev
Introducing Baseline Stay organized with collections Save and categorize content based on your preferences. At Google I/O 2023 we announced Baseline, learn more about this initiative and why we think it's important. Baseline helps you to see, at a glance, whether a feature or API is safe to use in your site or web applications. In this post, learn about the ideas that led to this concept, and how
Baseline features you can use today | Articles | web.dev
Baseline features you can use today Stay organized with collections Save and categorize content based on your preferences. The web is always evolving and browsers update constantly to give developers new tools to innovate on the platform. Things that previously required helper libraries become part of the web platform and supported on all browsers, along with shorter or easier ways to code design
Accessibility Support
Important: This website does not attempt to establish a standard for how assistive technologies must behave. Read the FAQ for more information. Additionally, this is a work in progress. Please submit feedback or suggestions. This a community driven effort. Please run some tests to help keep this project going and to learn about assistive technologies along the way.
Interop 2022: end of year update | Blog | web.dev
Interop 2022: end of year update Stay organized with collections Save and categorize content based on your preferences. We've reached the end of another year, and it's time to look at the improvements made by browsers as we work together to improve the interoperability of the web platform. You can check out how things started in our post in March this year, as the initiative was launched. The scor
Don't fight the browser preload scanner | Articles | web.dev
Don't fight the browser preload scanner Stay organized with collections Save and categorize content based on your preferences. Find out what the browser preload scanner is, how it helps performance, and how you can stay out of its way. One overlooked aspect of optimizing page speed involves knowing a bit about browser internals. Browsers make certain optimizations to improve performance in ways th
browserl.ist: A page to display compatible browsers from a browserslist string.
Shared browser compatibility config for popular JavaScript tools like Autoprefixer, Babel, ESLint, PostCSS, and Webpack Supported by Evil Martians and Cube Check compatible browsers How to get started Use defaults if you're building a web application for the global audience. Use node 18 if you're building a Node.js application, e.g., for server-side rendering. Autoprefixer, Babel and many other to
Chromeに実装された疑似クラス「:has()」がjQueryの「:has()」に悪影響、一定の条件下でWebサイトが壊れる可能性
Chromeに実装された疑似クラス「:has()」がjQueryの「:has()」に悪影響、一定の条件下でWebサイトが壊れる可能性 最近リリースされたSafariとChromeで、CSSのSelectors Level 4（現時点でドラフト）仕様にある疑似クラス「:has()」が相次いで実装されました。 疑似クラス「:has()」は、カッコ内に要素を書くと、その要素を持つ親要素にのみ指定したスタイルを設定できる、という便利な機能を提供してくれます。 ところがこの「:has()」のChromeにおける実装は、jQueryで似たような機能（カッコ内の要素を持つ親要素を選択する）を提供する「:has()」に悪影響を及ぼし、このjQueryの「:has()」を使っているWebサイトでは、Chromeを利用した場合に一定の条件下でWebサイトが壊れるなどの問題を引き起こすことが分かりました（同じエ
IE の歴史 | Yomotsu net
IE 1IE 1 は 1995 年の 8 月にリリースされました。 Spyglass 社から Mosaic のからライセンスを取得し、ほぼそのまま Mosaic をベースに IE 1 をリリースしました。About Internet Explorer を開くと Mosaic ベースであることが記載されています。 IE 1 は Windows には組み込まれておらず、$49 の Microsoft Plus ! という別売りのパッケージの一部として売られていました。IE 1 は HTML1 や TCP/IP などに対応した素朴な Web ブラウザーで、1 MB ほどのプログラムでした。Mosaic から始まったというのは、つまり Firefox と兄弟とも言えるわけですね。（Firefox は Netscape の後継ブラウザーであり、Netscape は Mosaic を開発したマーク・ア
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
A modern approach to browser support
Web Platform Status
Baseline progressive enhancement
HTMLソースコードから個人情報が筒抜け？ Chromeなどのブラウザ拡張機能の多くで脆弱性 米研究者らが発見
web-platform-tests dashboard