- From: mikemcguire via GitHub <sysbot+gh@w3.org>
- Date: Mon, 06 Nov 2017 21:04:54 +0000
- To: public-css-archive@w3.org
Im not going to pretend to understand the difficulties in implementing the client code cause I'm completely unqualified. But want to put my two cents in. When I ran into this issue I sat stumped forever. While this issue is now well documented on the web, it took me forever to actually figure out that the transform is what was causing the issue and thus being able to find the chrome bug filed and eventually the original Bugzilla spec bug to request an update. It seems counter-intuitive to not update the spec with what seems to be a universal expectation to accommodate the Chrome team. Especially since other browsers are accommodating what seems to be universally expected. Additionally, while the spec for positioned elements outlines this issue, I find it difficult to understand the language used in the spec. Front-end devs could potentially waste a lot of time looking for a fix, and possibly explains a lack of interest for this issue. I personally find that the transforms spec more clearly outlines the behavior than the positioning spec. -- GitHub Notification of comment by mikemcguire Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/913#issuecomment-342286257 using your GitHub account
Received on Monday, 6 November 2017 21:05:04 UTC