Status update: quoting [this comment in D193612](https://phabricator.services.mozilla.com/D193612#6424648): > Hmmm…the latest Try push I've submitted with [D193682](https://phabricator.services.mozilla.com/D193682) included ([try:440344eacf9b](https://treeherder.mozilla.org/jobs?repo=try&tier=1%2C2%2C3&revision=440344eacf9b357a9af696a99df25e3abff8ad16)) has not worked as I'd hoped. The decision to initialize WebGPU does not seem like something we can easily live-update with current code. Trying to change this seems to entail a bunch of design decisions that are a distraction from the core of this problem, which is that we expect hardware that supports MacOS 10.15 to be compatible with WebGPU, and _not_ blocklisted[^1]. > > I'd prefer to explore other options like fixing our blocklist before going further down this hacky path. Abandoning for now. > > --- > > [^1]: Examples: How do we transition currently open tabs when this preference changes?
Bug 1864698 Comment 7 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Status update: quoting [this comment in D193612](https://phabricator.services.mozilla.com/D193612#6424648): > Hmmm…the latest Try push I've submitted with [D193682](https://phabricator.services.mozilla.com/D193682) included ([try:440344eacf9b](https://treeherder.mozilla.org/jobs?repo=try&tier=1%2C2%2C3&revision=440344eacf9b357a9af696a99df25e3abff8ad16)) has not worked as I'd hoped. The decision to initialize WebGPU does not seem like something we can easily live-update with current code. Trying to change this seems to entail a bunch of design decisions that are a distraction from the core of this problem, which is that we expect hardware that supports MacOS 10.15 to be compatible with WebGPU, and _not_ blocklisted[^1]. > > I'd prefer to explore other options like fixing our blocklist before going further down this hacky path. Abandoning for now. > > --- > > [^1]: Examples: How do we transition currently open tabs when this preference changes? Will un-assign this bug from myself once the test expectations patch I landed in `autoland` makes it to `central`.
Status update: quoting [this comment in D193612](https://phabricator.services.mozilla.com/D193612#6424648): > Hmmm…the latest Try push I've submitted with [D193682](https://phabricator.services.mozilla.com/D193682) included ([try:440344eacf9b](https://treeherder.mozilla.org/jobs?repo=try&tier=1%2C2%2C3&revision=440344eacf9b357a9af696a99df25e3abff8ad16)) has not worked as I'd hoped. The decision to initialize WebGPU does not seem like something we can easily live-update with current code. Trying to change this seems to entail a bunch of design decisions that are a distraction from the core of this problem, which is that we expect hardware that supports MacOS 10.15 to be compatible with WebGPU, and _not_ blocklisted[^1]. > > I'd prefer to explore other options like fixing our blocklist before going further down this hacky path. Abandoning for now. > > --- > > [^1]: Examples: How do we transition currently open tabs when this preference changes? :jimb, I think we simply need to focus on fixing the blocklist, but this is not something I have experience with. NI'ing you for help here, since I _think_ it shouldn't be a huge lift. Will un-assign this bug from myself once the test expectations patch I landed in `autoland` makes it to `central`.