Closed Bug 1266316 Opened 8 years ago Closed 6 years ago

Maybe change our serialization of clip-path shapes once the spec defines what should happen

Categories

(Core :: Layout, defect, P3)

defect

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: jwatt, Unassigned)

References

(Blocks 1 open bug)

Details

Attachments

(1 file, 1 obsolete file)

Once the following is addressed in the spec we should modify our serialization of clip-path shapes if appropriate.

https://lists.w3.org/Archives/Public/public-fx/2016AprJun/0000.html
https://github.com/w3c/fxtf-drafts/issues/3
Summary: Change the serialization of clip-path shapes one the spec defines what should happen → Maybe change our serialization of clip-path shapes once the spec defines what should happen
Attached patch strawman patch (obsolete) — Splinter Review
If the decision is that we should omit the <geometry-box> when a shape is present that causes a problem for us. We would want to ideally change this code something like this, but at this point we have no knowledge of whether a shape was specified too.
Attached patch strawman patchSplinter Review
Attachment #8743696 - Attachment is obsolete: true
Jonathan, r u still currently working on this ?
Flags: needinfo?(jwatt)
Priority: -- → P3
I'm not, no. Do you have someone who could take it?
Flags: needinfo?(jwatt)
Yes, will do.
Assignee: jwatt → nobody
Blocks: basic-shape
jwatt, from the last feedback from dirk on GitHub, do you have any other concerns ?


Besides, I've done couple tests on <basic-shape> serialization for clip-path, it seems the result is a bit different from what spec defined[1]. If we want to align, I will create follow-up bugs to do that.

[1]examples in https://www.w3.org/TR/css-shapes-1/#basic-shape-serialization
Flags: needinfo?(jwatt)
Assignee: nobody → cku
See Also: → 1288626
(In reply to Astley Chen [:astley] (UTC+8) from comment #6)
> jwatt, from the last feedback from dirk on GitHub, do you have any other
> concerns ?
> 
> 
> Besides, I've done couple tests on <basic-shape> serialization for
> clip-path, it seems the result is a bit different from what spec defined[1].
> If we want to align, I will create follow-up bugs to do that.
> 
> [1]examples in https://www.w3.org/TR/css-shapes-1/#basic-shape-serialization

Could you update your test cases here?
Flags: needinfo?(aschen)
https://drafts.csswg.org/css-shapes-1/#shape-outside-property

Computed value:
  as defined for <basic-shape> (with <shape-box> following, if supplied)...

In current implementation, clip-path's behavior is aligned with shape-outside.  Unless spec changes to what jwatt mentioned in comment 1, current implementation of reference box serialization is correct.
And I don't think this issue block clip-path basic shape shipping.
No longer blocks: basic-shape-ship
(In reply to Astley Chen [:astley] (UTC+8) from comment #6)
> jwatt, from the last feedback from dirk on GitHub, do you have any other
> concerns ?

I'll take another look at this today or tomorrow. I need to page the background to this issue back in and think about what Dirk said.
Flags: needinfo?(aschen)
I'll suggest filing a spec issue to follow up the discussion here.
Status: NEW → ASSIGNED
Assignee: cku → nobody
Status: ASSIGNED → NEW
Looks okay now.
Status: NEW → RESOLVED
Closed: 6 years ago
Flags: needinfo?(jwatt)
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: