674804 - (css-exclusions-1) [META] Implement CSS Exclusions Module Level 1

Status: UNCONFIRMED

(Core :: Layout, enhancement)

Description

[Aaron Kaluszka]

Implement Adobe's CSS Exclusions proposal for more complex layouts like those used in print. This is still in flux, but Adobe has created a WebKit-based prototype found here: http://labs.adobe.com/technologies/cssregions/

Comment 1

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

The exclusions proposal has been merged into the floats proposal; I'm against the lot of it.

Comment 2

[Florian Bender]

Exclusions is back, please reopen.

Comment 3

[Florian Bender]

Would you mind reopening, please?

Comment 4

[Florian Bender]

(In reply to Florian Bender from comment #3)
> Would you mind reopening, please?
I can do that myself now :)

So, according to MSDN, this is already in IE10. Also, Apple showed this on WWDC, and Chrome has it, too. Some tests say Firefox has limited support, but that's mostly for an outdated spec, AFAICS, as the tests linked to in the URL (above) all failed in my Fx 25b.

Comment 5

[Karl Dubost💡 :karlcow]

* Blink Chrome  https://bugs.chromium.org/p/chromium/issues/detail?id=234749 Status: Archived
                https://www.chromestatus.com/features/6296903092273152
* WebKit Safari http://trac.webkit.org/changeset/166618 (Remove exclusions parsing support)
                https://bugs.webkit.org/show_bug.cgi?id=131046

Comment 6

[Jen Simmons [:jensimmons]]

I'd like to discuss Exclusions, and see why folks have been against it. Perhaps the spec needs a new approach. But the end result for Authors would be incredibly helpful. And would stop designers from demanding non-accessible websites are built in order to accomplish their graphic design ideas. NYTimes, MPR, many big editorial sites have broken a11y because they don't have a tool like Exclusions.

Comment 7

[Sebastian Zartner [:sebo]]

Turning this into a meta-issue for all the things that are covered by the CSS Exclusions Module Level 1 spec.

Sebastian

Comment 8

[Jonathan Watt [:jwatt]]

Mass bug change to replace various 'parity' whiteboard flags with the new canonical keywords. (See bug 1443764 comment 13.)

Comment 9

[wig_2006]

In present , All user usage in CSS Exclusions Level 1 at https://caniuse.com/css-exclusions have 0.9% use , I hope manufacturer to add support CSS Exclusions Level 1 to add all user usage in CSS Exclusions Level 1 to more than 10%.

Picture to descirbe all user usage percent - https://i.postimg.cc/TRFtCrKZ/css-exclusion-art-scale-4-00x-gigapixel.jpg

Comment 10

[Axel]

Is there a way to vote for having CSS Exclusions implemented?

I'm looking for a layout solution for this:
https://stackoverflow.com/questions/71309726/how-can-i-have-a-block-float-centered-having-text-surround-it-to-both-sides

Comment 11

[Sebastian Zartner [:sebo]]

(In reply to Axel from comment #10)

Is there a way to vote for having CSS Exclusions implemented?

Yes! There's a button at the top of every bug that allows to vote for it.

(In reply to wig_2006 from comment #9)

In present , All user usage in CSS Exclusions Level 1 at https://caniuse.com/css-exclusions have 0.9% use , I hope manufacturer to add support CSS Exclusions Level 1 to add all user usage in CSS Exclusions Level 1 to more than 10%.

The CSS Exclusions 1 specification is still in a very early state and also not updated for a long time. Before the implementation for this can start, the specification needs to be revised and possible issues be sorted out. So I suggest you reach out the CSS Working Group or explicitly the spec. authors first.

Note that I am not related to Mozilla, so maybe someone else here may provide different info regarding this.

Sebastian

Comment 12

[Thomas Wisniewski [:twisniewski]]

Removing the parity-* flags, as Chrome, Edge and Safari no longer support CSS exclusions.