This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 27464 - Resolving units when filterUnits="objectBoundingBox"
Summary: Resolving units when filterUnits="objectBoundingBox"
Status: RESOLVED INVALID
Alias: None
Product: CSS
Classification: Unclassified
Component: Filter Effects (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Dean Jackson
QA Contact: public-css-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-11-28 12:22 UTC by Erik Dahlström
Modified: 2015-02-11 04:37 UTC (History)
4 users (show)

See Also:


Attachments

Description Erik Dahlström 2014-11-28 12:22:07 UTC
http://www.w3.org/TR/filter-effects-1/#FilterUnitsAttribute says:

"If filterUnits is equal to objectBoundingBox, then x, y, width, height represent fractions or percentages of the bounding box on the referencing element (see object bounding box units)."

Now, if we take an example of a valid <length> for the x attribute, say "47em", how should that be interpreted in the case of filterUnits="objectBoundingBox"?

I think the author's expection might be that 47em is kept as just that, but actually what happens is that it gets computed into user units and then taken as a fraction of the boundingbox.

Therefore I'd like to ask that the behavior is clarified such that it becomes more obvious that this happens.
Comment 1 Dirk Schulze 2015-02-11 04:37:50 UTC
As discussed in the FX meeting (http://www.w3.org/2015/02/10-fx-irc) there is nothing that we need to change in Fitler Effects. CSS specifies this case sufficiently.