{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreicwmml5jxy4yb7ryvrfhwcd7hxypbyifiwyosqz63r3pyxpjmdone",
    "uri": "at://did:plc:hqad6xwuzg7oqfmwylfkvqfm/app.bsky.feed.post/3miwdbdrjenb2"
  },
  "path": "/viewtopic.php?t=33306&p=271988#p271988",
  "publishedAt": "2026-04-07T13:44:38.000Z",
  "site": "http://forum.palemoon.org",
  "textContent": "> --enable-jxl is no longer a valid mozconfig flag, because JPEG XL support is always built and that flag has been no-op for a pretty long time now. You should remove it.\n\nYeah, after removing that option from **.mozconfig** half-time in the build process I noticed **libmedia_libjxl** being built. Now forgive me for sounding like a Vulcan but breaking the building process due to a **redundant** option seems... illogical. The logical way would be to add all such redundant/obsolete options to an internal list, and when any of them is encountered **just notify the user about its status** - do it in bold red font if necessary - and let the build continue normally.\n\nI wonder, would that option's counterpart ( --disable-jxl ) be available and valid? Who knows, maybe someone would want/need it for whatever reason.\n\n* * *",
  "title": "Browser Development • Re: 34.2.0 build failed, --enable-jxl unknown ??",
  "updatedAt": "2026-04-07T13:44:38.000Z"
}