[Webkit-unassigned] [Bug 72584] Support Image Level 3's image() notation

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu Sep 12 15:31:34 PDT 2013


--- Comment #52 from Dirk Schulze <krit at webkit.org>  2013-09-12 15:30:43 PST ---
(In reply to comment #51)
> > > > I thought image() was in CSS3 Images, but looks like it was dropped and delayed to CSS4.
> > > 
> > > Actually I'm pretty sure (see the spec I mentioned in the changelog) it's still in CSS3 images, the part that was deferred to CSS4 images is the rtl/ltr stuff. But maybe I've got that wrong because I find the standards process completely incomprehensible.
> > 
> > Oh you are right. In this case r- for prefixing the function!!!! The spec is in CR and should be implemented unprefixed. You may can add a compiler flag if you want to. IIRC you did not announce implementing image() on webkit-dev anyway.
> Just because something is in CR doesn't mean we implement it without a prefix? We should only do that if we are extremely certain it won't change (which I don't think we are).  This is an experimental feature, and should be treated as such.

The CSS WG charta is clear about that. If a specification is in CR, it shall be (might even be a must) implemented without prefix.

It is unlikely that a specification that is in CR will change drastically. This was not the case so far. CR is requiring implementations and implementation feedback.

A future spec might add functionality to features but this must be in a compatible way.

If you worry that we reveal problems with image() on the way of implementing it, we should do it behind a compile time flag.

Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the webkit-unassigned mailing list