Raindrop.io Bookmarks 2026-01-07

2026年1月7日

• How Apple's Key Tactic Could Prevent Japan's Smartphone Act from Improving Browser Competition - Open Web Advocacy

  "TL;DR: Japan's new Smartphone act requires that Apple allow browser vendors to use their own engines in Japan. However, Apple looks set to use the same tactic it has used in the EU to avoid complying with the same provision of the Digital Markets Act for the last twenty-one months."

• An Abridged History of Safari Showstoppers - Webventures

  "TL;DR: iOS Safari is more than an inconvenience for developers, it's the fundamental reason interoperability has been stymied in mobile ecosystems; frequent showstopping bugs, a large patch gap, and lack of competing engines ensures the web is not a credible competitor to native. Here are the receipts to prove it."

• 2025 JavaScript Rising Stars

  "What a year it has been! From the explosion of AI agents transforming how we build applications to critical vulnerabilities and security attacks that shook the ecosystem, 2025 has been a year of both remarkable innovation and sobering challenges."

• Disco

  "Discovering the next great AI features for the web"

• How I Evaluate an ACR (VPAT®) -- Adrian Roselli

  "ACRs are Accessibility Conformance Reports, which are the output of a VPAT, or Voluntary Product Accessibility Template maintained by ITIC, or the Information Technology Industry Council (which is why VPAT often has a ® symbol hanging off it). An organization may fill out the template to indicate how or if its offering conforms to WCAG, Section 508, EN 301 549, or all three."

• Pronunciation Lexicon Specification (PLS) Version 1.0

  "The Pronunciation Lexicon Specification (PLS) is designed to enable interoperable specification of pronunciation information for both ASR and TTS engines. The language is intended to be easy to use by developers while supporting the accurate specification of pronunciation information for international use."

• How to @scope CSS Now That It's Baseline - Frontend Masters Blog

  "Personally, I like splitting CSS into reusable modules, including them as internal CSS using templating logic only when needed (e.g., forms.css on /contact), and then using in-HTML scoped <style>s for one-time or once-per-page components. That way we can avoid render-blocking external CSS without causing Cumulative Layout Shift (CLS) and still have fairly organized CSS. One thing to consider though is that CSS isn't cached with these methods, so you'll need to determine whether they're worth that."