{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreicvfyatv7zdvicdr7dngd3l2bhk4wzxshx7c37xm2jjgmuwki4xs4",
    "uri": "at://did:plc:hqad6xwuzg7oqfmwylfkvqfm/app.bsky.feed.post/3mj6wsgt77pe2"
  },
  "path": "/viewtopic.php?t=32045&p=272180#p272180",
  "publishedAt": "2026-04-10T19:36:56.000Z",
  "site": "http://forum.palemoon.org",
  "tags": [
    "working draft",
    "https://registry.khronos.org/webgl/specs/1.0.3/#5.2"
  ],
  "textContent": "> > Pale Moon’s implementation of WebGLRenderingContext.getContextAttributes() is missing the powerPreference field that Firefox (version 100+) and other modern browsers include.\n>\n> It should be noted that the powerPreference field they're saying is currently only in a working draft (annoyingly there doesn't seem to be a permalink for this current version of the working draft). It is currently not available in the latest WebGL specification (1.0.3): https://registry.khronos.org/webgl/specs/1.0.3/#5.2\n>\n> It doesn't matter that Firefox 100 has implemented it. Cloudflare is just simply forcing the implementation of **draft** features we haven't even heard about (because we don't care about turning the web browser into a third-rate, insecure replacement of the operating system that mainstream is doing)\n\nReading that spec looks a bit of a good way to break things, as they've dropped one tag and added 2 new ones. Which means if an older program talks to a new browser, they're not going to get something they expect, and vice versa. I thought when one was going for backward compatibility, one didn't drop members of dictionaries. That should require a major version number increase.\n\n* * *",
  "title": "Browser Support • Re: Cloudflare Verification Loop issues",
  "updatedAt": "2026-04-10T19:36:56.000Z"
}