Closed Bug 1535808 Opened 10 months ago Closed 10 months ago

EXT_float_blend restrictions break some content

Categories

(Core :: Canvas: WebGL, defect, P1, major)

defect

Tracking

()

VERIFIED FIXED
mozilla67
Tracking Status
firefox-esr60 --- unaffected
firefox66 --- unaffected
firefox67 + fixed
firefox68 --- fixed

People

(Reporter: jgilbert, Assigned: jgilbert)

References

Details

(Keywords: dev-doc-complete, regression, Whiteboard: gfx-noted)

Attachments

(1 file)

The WebGL WG has decided to implicitly enable this extension.

A TODO from this is to warn when implicitly-enabled extensions are used.

Blocks: 1535809

Chrome team reports that some content is broken being strict about this
validation. Implicitly enable it to preserve functionality.

Status: NEW → ASSIGNED

We should mention this in the docs and the warning could link to the docs for more information (many warnings have [Learn more] links pointing to MDN which web devs find useful).

Keywords: dev-doc-needed

PR merged, this ext is now exposable.

Pushed by jgilbert@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/711d5fdae7b2
Expose and implicitly enable EXT_float_blend. r=lsalzman

[Tracking Requested - why for this release]:
Content will break (compared to Chrome) if this fix doesn't make it into 67.

Thanks for the heads up. Jeff, once this has landed on central and is verified as fixed, please do an uplift request for our next beta. Would that fix benefit from manual verification from our QA team?

Flags: needinfo?(jgilbert)
Status: ASSIGNED → RESOLVED
Closed: 10 months ago
Resolution: --- → FIXED

(In reply to Pascal Chevrel:pascalc from comment #7)

Thanks for the heads up. Jeff, once this has landed on central and is verified as fixed, please do an uplift request for our next beta. Would that fix benefit from manual verification from our QA team?

The patch includes tests, so we don't need manual verification.

Flags: needinfo?(jgilbert)
Status: RESOLVED → VERIFIED

Comment on attachment 9051470 [details]
Bug 1535808 - Expose and implicitly enable EXT_float_blend.

Beta/Release Uplift Approval Request

  • Feature/Bug causing the regression: Bug 1522018
  • User impact if declined: Some incorrectly-written non-portable content will break as compared to Chrome.
  • Is this code covered by automated tests?: Yes
  • Has the fix been verified in Nightly?: Yes
  • Needs manual test from QE?: No
  • If yes, steps to reproduce:
  • List of other uplifts needed: none
  • Risk to taking this patch: Low
  • Why is the change risky/not risky? (and alternatives if risky): We have automated tests for this, and the patch was written against 67 to begin with, but didn't land before the marge.
  • String changes made/needed: none
Attachment #9051470 - Flags: approval-mozilla-beta?

Comment on attachment 9051470 [details]
Bug 1535808 - Expose and implicitly enable EXT_float_blend.

Fix and tests to prevent a WegGL webcompat problem when 67 ships, already fixed and verified on Nightly, uplift approved for 67 beta 4, thanks!

Attachment #9051470 - Flags: approval-mozilla-beta? → approval-mozilla-beta+

Note to MDN team:

I've written a release note about this in the Fx67 rel notes: https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Releases/67#Canvas_and_WebGL

As for other docs work, I think we just need to update the BCD for this feature.

Updated https://developer.mozilla.org/en-US/docs/Web/API/EXT_float_blend with new details.

BCD was claiming that EXT_float_blend was added in Firefox 67, which is good, but that it was behind a pref, which is not correct, so I've fixed that and submitted BCD PR 4105.

You need to log in before you can comment on or make changes to this bug.