- From: Tobi Reif via GitHub <sysbot+gh@w3.org>
- Date: Tue, 13 Sep 2016 10:49:58 +0000
- To: public-svg-issues@w3.org
I think I'll be able to handle the issue in some way when the re-ordering happens. But I hope you will be able to improve SVG (SVG2) by making sure that your users won't be surprised by the side effects, and won't have to read the spec just for setting opacity without changing the stacking order, and won't be tempted to use the published hackish workaround(s). A user of eg SVG2 who is (eg using z-index and) setting/changing opacity shouldn't have to worry about the various possible reasons why the *opacity* property could affect *stacking order*. (Ditto for any other properties which have side-effects.) If you can't fix the existing property by ensuring it is side-effect free, please consider offering a new property that is side-effect free. (If necessary make it independent of "grouping" etc. Anything that's necessary to make it 100% side-effect free.) Setting/changing that property would be guaranteed to affect opacity and nothing else. It would do what its name says and would not cause problems by doing more than it says it does. (And yes, it would also be great if the Chrome and WebKit bugs could get fixed, but as you say that's not in scope for a spec ticket.) -- GitHub Notification of comment by tobireif Please view or discuss this issue at https://github.com/w3c/svgwg/issues/264#issuecomment-246644663 using your GitHub account
Received on Tuesday, 13 September 2016 10:50:06 UTC