Dated Draft: https://www.w3.org/TR/2013/WD-css-transforms-1-20131126/
Editor's Draft: http://drafts.csswg.org/css-transforms-1/
The following color coding convention is used for comments:
Open issues are marked like this
An issue can be closed as Accepted
, OutOfScope
,
Invalid
, Rejected
, or Retracted
.
Verified
indicates commentor's acceptance of the response.
Issue 1. # Summary: Issues list link is outdated From: Rick Byers Comment: https://github.com/w3c/csswg-drafts/issues/486 Response: Open: =ED= Edit. Resolved: Editorial
Issue 2. # Summary: Add more info to “Module Interactions” From: Dirk Schulze Comment: https://www.w3.org/Bugs/Public/show_bug.cgi?id=17237 Response: https://github.com/w3c/csswg-drafts/issues/914 Open: =ED= Edit. Resolved: Editorial
Issue 3. # Summary: Convert to <*-percentage> notation From: Sebastian Zartner (SebastianZ) Response: https://github.com/w3c/csswg-drafts/issues/645 Open: =ED= Edit. Resolved: Editorial.
Issue 4. # Summary: Define transform list using grammar From: Sebastian Zartner Comment: https://www.w3.org/mid/CAERejNZgyWKV5ioh3KR9BmYYrvpM5919D9z1Qb-LjQ5zBGOFuQ@mail.gmail.com Response: http://www.w3.org/mid/CAAWBYDCB7nP+rqj7DzAef6zqMHtvoshLGMJuL7PsMi-V9qvPfw@mail.gmail.com Closed: Invalid
Issue 5. # Summary: Clarify matrix index convention From: Maurizio Casimirri Comment: http://www.w3.org/mid/C73D086A-A220-48E3-A3DC-6195D350C3FA@gmail.com Response: https://github.com/w3c/csswg-drafts/issues/924 Open: =ED= Edit. Resolved: Editorial
Issue 6. # Summary: Confusion about multiplication From: Simon Sapin & Boris Zbarsky Comment: https://www.w3.org/mid/509FCC62.5080101@mit.edu Response: https://github.com/w3c/csswg-drafts/issues/909 Open: =ED= Make sure comments in thread are all addressed Resolved: Bugfix
Issue 7. # Summary: Application of transform to inlines From: Gérard Talbot Comment: https://www.w3.org/mid/b464220dd959f9a9f808dd4aad85288e@gtalbot.org Comment: http://www.w3.org/mid/20140210195906.GA18205@crum.dbaron.org Response: https://github.com/w3c/csswg-drafts/issues/908 Open: =ED= Propose text, add to agenda for WG resolution. Resolved:
Issue 8. # Summary: Computed Style of 'transform' From: Dirk Schulze Comment: https://www.w3.org/mid/A020C5AD-51B0-4288-8D8A-9D8322213D5B@adobe.com Comment: http://www.w3.org/mid/20140325212945.GA26872@crum.dbaron.org Response: http://www.w3.org/mid/314879EA-CF63-4792-90DD-36000224B04F@adobe.com Open: =ED= Fixed Resolved: Bugfix Verified: [need a response where dbaron says it's all good now]
Issue 9. # Summary: Error in order of multiple transform function From: rosenau Comment: https://www.w3.org/Bugs/Public/show_bug.cgi?id=29110 Response: https://github.com/w3c/csswg-drafts/issues/909. Open: =ED= Edit. Resolved: Bugfix
Issue 10. # Summary: Clarify behavior for gradientTransform and patternTransform From: Erik Dahlström Comment: https://www.w3.org/Bugs/Public/show_bug.cgi?id=26470 Response: https://github.com/w3c/csswg-drafts/issues/919 Open: =Dirk= Deal. or =WG= Discuss.
Issue 11. # Summary: Use of “containing block” does not match CSS2.1 definition From: Aryeh Gregor From: Simon Sapin Comment: https://www.w3.org/Bugs/Public/show_bug.cgi?id=16328 Comment: http://www.w3.org/mid/514E058C.5060105@exyr.org Response: https://github.com/w3c/csswg-drafts/issues/913 Notes: See also dbaron's message in the issue below. Open: =ED= Figure out what to do. https://github.com/w3c/csswg-drafts/issues/913 Resolved: Editor discretion (or agenda+ if there's a problem)
Issue 12. # Summary: Spec doesn't mention establishing abspos containing block From: Robert O'Callahan Comment: https://www.w3.org/mid/24BE3FE7-60C9-4690-A01C-F2291460DE7F@adobe.com From: David Baron Comment: https://www.w3.org/mid/20151125002414.GA22745@pescadero.dbaron.org Response: https://github.com/w3c/csswg-drafts/issues/919 Open: =ED= Edit. Resolved: Bugfix
Issue 13. # Summary: Interaction of regions and transforms and abspos/fixedpos From: Mihnea-Vlad Ovidenie Comment: https://www.w3.org/mid/CE4E28E9.4B01C%25mihnea@adobe.com Response: =astearns= File against Regions Closed: Out-of-Scope
Issue 14. # Summeray: Specify stack level of non-positioned transformed elements From: Øyvind Stenhaug Comment: http://www.w3.org/mid/op.wg8psjr1bunlto@oyvinds-desktop Response: https://github.com/w3c/csswg-drafts/issues/925 Changes: Open: =ED= Edit. Resolved: Bugfix
Issue 15. # Summary: Clarify Appendix E rendering of 3D transformed descendants From: David Baron Comment: http://www.w3.org/mid/20150904234527.GA15137@pescadero.dbaron.org Response: https://github.com/w3c/csswg-drafts/issues/926 Changes: Open: =ED= Edit. Resolved: Bugfix
Issue 16. # Summary: transform functions should accept percentages From: Boris Zbarsky Comment: https://www.w3.org/mid/546F5D45.6030704@mit.edu Response: https://www.w3.org/mid/A2D81F68-B51F-468C-8C10-50D435980254@adobe.com Closed: Accepted Resolved: Bugfix
Issue 17. # Summary: Define basis for percentage transform on patterns, gradients, clipPath From: Dirk Schulze Comment: http://www.w3.org/mid/9B0DDCB4-B480-471F-943A-C5ED00598DFA@adobe.com Response: https://github.com/w3c/csswg-drafts/issues/892 Open: =WG= Discuss.
Issue 18. # Summary: Match SVG spec for interaction with object bounding box units From: Amelia Bellamy-Royds Comment: https://www.w3.org/Bugs/Public/show_bug.cgi?id=28385 Response: https://github.com/w3c/csswg-drafts/issues/922 Changes: Open: =ED= Edit. https://github.com/w3c/csswg-drafts/issues/922 Resolved: Editor discretion.
Issue 19. # Summary: Update “transformable elements” for SVG2 From: Nikos Andronikos Response: https://github.com/w3c/csswg-drafts/issues/358 Changes: Open: =ED= Edit Resolved: Editor discretion
Issue 20. # Summary: Units aren't back-compatible with old SVG From: Dr. Olaf Hoffman Comment: https://www.w3.org/mid/201204211629.13408.Dr.O.Hoffmann@gmx.de Response: https://www.w3.org/mid/3DCACD7B-0115-44FC-901A-A86DC1211CD1@adobe.com Closed: Rejected Resolved: Editor discretion
Issue 21. # Summary: Unitless values From: Tab Atkins Comment: http://www.w3.org/mid/CAAWBYDDDDMY0czypkLQ2X8tBtLFjYn5t9g+aYOPBzXLEAGzBzA@mail.gmail.com Comment: http://www.w3.org/mid/CAAWBYDD3VfCvDfe0TEUJEd7e+JXZzhRDGTyEgdc9Hodz0pCLUQ@mail.gmail.com Open: =ED= Edit. Resolved: =WG= Resolve.
Issue 22. # Summary: Transform syntax CSS vs SVG harmonization From: Dirk Schulze Comment: http://www.w3.org/mid/7E680372-9199-4AF9-98A1-C7B6ECB72C87@adobe.com Response: https://www.w3.org/mid/88568E75-27C9-4DA4-BCD6-7459FA5D9FE4@adobe.com Open: Accepted Resolved: =WG= Review.
Issue 23. # Summary: User coordinate space statement breaks SVG From: Amelia Bellamy-Royds Comment: http://www.w3.org/mid/CAFDDJ7yhF7Qn28wVMqb7ra6N9Q=j74OTqHWpjLeYrH=LQwmd4A@mail.gmail.com Response: https://github.com/w3c/csswg-drafts/issues/893 Open: =WG= Discuss.
Issue 24. # Summary: Issues with transform on SVG root From: Dirk Schulze Comment: https://www.w3.org/mid/0A9D2705-9FFE-425B-B3CB-297EA97D337D@adobe.com Open: =SVGWG= Figure out if anything remains to be done.
Issue 25. # Summary: Transforms on root SVG element From: Amelia Bellamy-Royds Comment: http://www.w3.org/mid/CAFDDJ7xQp+j2c+18zkRyPWPtnuk+dbVA6Dc_L7ACr-tptAGicA@mail.gmail.com Response: https://github.com/w3c/csswg-drafts/issues/894 Open: =WG= Discuss with SVG folks
Issue 26. # Summary: Use UA style sheet instead of prose for SVG transform-origin From: Dirk Schulze Comment: https://www.w3.org/Bugs/Public/show_bug.cgi?id=28000 Comment: https://www.w3.org/mid/20150611085235.GA3929@wok.mcc.id.au Response: https://www.w3.org/mid/CE3AFDB0-D260-493A-9110-16BB01D8E28E@adobe.com Response: https://github.com/w3c/csswg-drafts/issues/920 Open: =ED= Edit. Resolved: Editor discretion
Issue 27. # Summary: Specs disagree on whether transform-origin's resolved value is used or computed From: Xidorn Quan Comment: https://github.com/w3c/csswg-drafts/issues/392#issuecomment-238494067 Proposal: https://github.com/w3c/csswg-drafts/issues/392#issuecomment-269639534 Response: Changes: https://github.com/w3c/csswg-drafts/commit/2317722f3b9165fdb7f69c990f4f3981682d31bf Closed: Accepted Resolved: https://lists.w3.org/Archives/Public/www-style/2017Feb/0048.html
Issue 28. # Summary: transform-origin relative to containing block From: Xidorn Quan Comment: https://www.w3.org/mid/CAMdq698_DMux4CFD6pA2MOdK7VX9yCWJgciXE0_MuRxXAV1WMA@mail.gmail.com Response: https://www.w3.org/mid/CAMdq698unKqMTgJpVXFmRtcmcjfwEkhGfmhhk0dsZgxiQ4E6uQ@mail.gmail.com Closed: Retracted
Issue 29. # Summary: Add transform-origin-x/y? From: Boris Zbarsky Comment: https://www.w3.org/mid/50648288.4050309@mit.edu Response: Note: CSS Backgrounds L4 solved the logical coords problem since this thread was last discussed. Closed: Deferred to L2 Resolved: https://lists.w3.org/Archives/Public/www-style/2017Feb/0048.html & https://lists.w3.org/Archives/Public/www-style/2017Feb/0054.html
Issue 30. # Summary: transform-origin: 0% not equivalent to 0px is confusing From: Cameron McCormack Comment: https://www.w3.org/mid/525F2287.8050002@mcc.id.au Response: https://github.com/w3c/csswg-drafts/issues/895 Open: =WG= Discuss. (SVG) Notes: https://lists.w3.org/Archives/Public/www-style/2017Feb/0048.html Resolved:
Issue 31. # Summary: exact definition of origin argument to rotate() From: Rik Cabanier Comment: http://www.w3.org/mid/CAGN7qDC=oAU5XQt0E7sJ=2vcMLU1BzmH4L7EzYsfvtL-5LbHZQ@mail.gmail.com Comment: http://www.w3.org/mid/CAKA+Axk=-C3tTdoKRU3g2Be=GV3aeiNfqYot3205h6fZVP2K=w@mail.gmail.com Comment: http://www.w3.org/mid/CAGN7qDD9LftfaCqnH_oPXe78GqYv2aOdE8forTWN515=-UHRmg@mail.gmail.com Proposal: http://www.w3.org/mid/CAGN7qDAw3eU72K-QSeMVmqPjh0_wihnBf7rG4bsVsQnfVSDJ5g@mail.gmail.com Changes: [link to relevant section(s)] Closed: Invalid (rotate with > 1 argument removed) Resolved: https://lists.w3.org/Archives/Public/www-style/2017Feb/0054.html.
Issue 32. # Summary: Unitless zero rotation From: Simon Fraser Comment: https://www.w3.org/Bugs/Public/show_bug.cgi?id=29413 Response: Open: =ED= Update to reference CSS Values 3 correctly. Resolved: https://lists.w3.org/Archives/Public/www-style/2017Feb/0054.html
Issue 33. # Summary: Make Rotation Less Weird in 3D transforms From: Shane Stephens Comment: https://www.w3.org/mid/CAGTfzwT8M0_c1Wnk5To1zRVtGXtuLzXbjkpDS55DC6T9dUTfKQ@mail.gmail.com Response: https://github.com/w3c/csswg-drafts/issues/896 Notes: See also zero-coord axis issue below. Changes: Open: =shane= Investigate fixing quaternation algorithm per https://lists.w3.org/Archives/Public/www-style/2017Feb/0054.html Resolved:
Issue 34. # Summary: Reduce matrix decomposition when rotation axis has zero coord From: Shane Stephens Comment: http://www.w3.org/mid/CAGTfzwTS9r+z1LRu=3t25NW0A6yk0b+agaH6__8ZkcSD3-LR9A@mail.gmail.com Changes: Open: =ED= Edit & respond: rotate(x,x,x,0) acts like the id() function relative to other rotate functions. Resolved: https://lists.w3.org/Archives/Public/www-style/2017Feb/0054.html
Issue 35. # Summary: Interpolation of transform lists From: David Baron Comment: http://www.w3.org/mid/20120719213826.GA8775@crum.dbaron.org Response: http://www.w3.org/mid/474B73CD-95F5-467B-9F39-90D7045E3A9C@adobe.com Open: Accepted? Resolved: ? (dbaron unhappy with the state of the spec regarding the matching of the perspective() function) Verified: [get verification from dbaron]
Issue 36. # Summary: Add null transform as placeholder for animations? From: CSSWG Comment: http://www.w3.org/mid/523AB5BE.50406@inkedblade.net Response: https://github.com/w3c/csswg-drafts/issues/898 Response: Closed: Deferred Resolved: https://lists.w3.org/Archives/Public/www-style/2017Feb/0048.html
Issue 37. # Summary: Smarter interpolation of truncated transform lists From: Louis-Rémi Babé Comment: https://www.w3.org/mid/CALXxKfCKZd+P0mH2oFyDkBgps56WqwQnLSMpKk1nrqiFXScqVA@mail.gmail.com Response: https://www.w3.org/mid/CAAWBYDBPafEbiXNy=Mw4a9w1jmvK6dUJzq28PPjN7APgtjqAEw@mail.gmail.com Response: https://github.com/w3c/csswg-drafts/issues/927 Changes: Open: =shane= collect frequency data per https://lists.w3.org/Archives/Public/www-style/2017Feb/0048.html Resolved:
Issue 38. # Summary: Transform interpolation problem From: David Baron Comment: https://www.w3.org/mid/20140702002134.GA26687@crum.dbaron.org Response: Changes: Open: =ED= Clarify spec & respond to dbaron: Transitions will run whenever the functions differ, even if the endpoints are functionally identical. Resolved: https://lists.w3.org/Archives/Public/www-style/2017Feb/0048.html & https://lists.w3.org/Archives/Public/www-style/2017Feb/0054.html
Issue 39. # Summary: Interpolated values don't interpolate well with original start/end From: David Baron Comment: https://www.w3.org/mid/20140226234818.GA5390@crum.dbaron.org Changes: Open: =WG= Resolved Resolved: perpective() interpolates to perspective().
Issue 40. # Summary: Bugs in interpolation algorithm From: Manish Goregaokar (Manishearth) Comment: https://github.com/w3c/csswg-drafts/issues/483#issuecomment-249497761 Response: Changes: Open: =shane= investigate fixing algorithm per https://lists.w3.org/Archives/Public/www-style/2017Feb/0054.html Resolved: Bugfix.
Issue 41. # Summary: Matrix Interpolation From: Shane Stephens Comment: http://www.w3.org/mid/CADhPm3tF-tBQMwhOWRAYN-L+rVPhX-_xAa6ynKGa57Ue4HMywA@mail.gmail.com Notes: Might be further background elsewhere, didn't find it. But see below. Response: Changes: Open: Rejected =ED= Respond to thread. Resolved: https://lists.w3.org/Archives/Public/www-style/2017Feb/0054.html
Issue 42. # Summary: Use better matrix interpolation method From: Ken Shoemake From: Benoit Jacob Comment: http://www.w3.org/mid/52CD882F.6020408@yahoo.com Comment: http://www.w3.org/mid/CAJTmd9qXg+WAt5OK9g-pTEwHunEXxcKtvBSJ4fd_5=SmLHM-jg@mail.gmail.com Response: Open: =ED= Respond that while this does look better, for web compat reasons we can't change, and we'll continue to push things that make it easier to avoid matrix interpolation. Resolved: https://lists.w3.org/Archives/Public/www-style/2017Feb/0054.html
Issue 43. # Summary: Matrix Decomposition From: Dirk Schulze From: Rik Cabanier Comment: https://www.w3.org/mid/A54A72B2-5BFB-46F7-8B08-BE2B7A3EA8D2@adobe.com Comment: http://www.w3.org/mid/CAGN7qDBdtR1AWowudWzrj0ownknbvatv-HhC1E28_QJYSB47aQ@mail.gmail.com Open: Invalid =ED= Respond to explain why. Resolved: https://lists.w3.org/Archives/Public/www-style/2017Feb/0054.html
Issue 44. # Summary: Include Tagaki-san's definition of linear scale From: CSSWG Comment: http://www.w3.org/mid/CADhPm3sSRuNBNO8M_SUAp8BX7gnzCtBmmY9_bbm76xX2sU3N2g@mail.gmail.com Open: =ED= Make any necessary edits, respond to thread, and then close. Resolved: https://lists.w3.org/Archives/Public/www-style/2017Feb/0054.html
Issue 45. # Summary: getTransformToElement needs more detail From: CSSWG Comment: https://www.w3.org/mid/CADhPm3t+PxH+eCXcOxiX61J_Nx+jimkttsoViSCQNDSVOTKNDQ@mail.gmail.com Response: Changes: Open: =ED= Transfer to Geometry per WG resolution Resolved: https://lists.w3.org/Archives/Public/www-style/2017Feb/0054.html
Issue 46. # Summary: transform-box values & correspondence to SVG vs CSS From: Erik Dahlström Comment: https://www.w3.org/mid/op.x5otn9g7fwt8au@localhost.localdomain Response: https://github.com/w3c/csswg-drafts/issues/928 Comment: https://github.com/w3c/csswg-drafts/issues/857 Response: Notes: See also https://drafts.fxtf.org/paint/#fill-origin Open: =WG= Discuss, and ensure alignment with FXTF Paint. Resolved:
Issue 47. # Summary: Scrollbars vs. scaling down From: Tab Atkins Comment: https://www.w3.org/mid/CAAWBYDDX2ECLHm523xNpr8qqYgsqeU2SXiY0GvZo7S1063CoAg@mail.gmail.com Response: https://www.w3.org/mid/CAOp6jLYZ8VMPW4wNOMkH_uLPROr1ows22AFgLqMuhzQ=h89m0A@mail.gmail.com Comment: https://www.w3.org/mid/CAAWBYDDfy0ghxEB5jnSTP3LMTbGo1=p=Wq5GUizw3RySS6QGJA@mail.gmail.com Response: https://www.w3.org/mid/CAOp6jLYTvsqEYfUv=mfayYADuJnZKhC1vakfdqsFvrPu0Tp_7A@mail.gmail.com Closed: Invalid Verified: =ED= Verify.
Issue 48. # Summary: Impact of transforms on scrollable area (multiple threads) From: Robert O'Callahan Comment: http://www.w3.org/mid/CAOp6jLbN9SjQd4zRy=BcswPxzOR5RHvvshjdQ7Xb7zfyG1V6KA@mail.gmail.com animation Comment: https://www.w3.org/mid/CAOp6jLZZrmwZ1xZG2AzF+VTzn+zFUFa0EpSXp1T-fSc7ZhNa7A@mail.gmail.com Comment: https://www.w3.org/mid/CAOp6jLbbe9PWKfiooQ-jT+0E=zAd9VRqD-XqqCNogvDVmiBxaQ@mail.gmail.com animation Comment: https://www.w3.org/mid/CAOMQ+w9LYiOQ3u=DagEKEMqSeV91RqCMnUgy5zCaZsJw0Fur7g@mail.gmail.com Notes: See also https://drafts.csswg.org/css-overflow-3/#scrollable Notes: See also https://www.w3.org/mid/56415511.5090604@mozilla.com Open: =ED= Make edits per WG resolutions. Resolved: https://lists.w3.org/Archives/Public/www-style/2017Feb/0054.html
Issue 49. # Summary: Apply box-shadow after transform From: Christian Mayer Comment: https://www.w3.org/mid/56C63DB8.8080004@ChristianMayer.de Response: https://www.w3.org/mid/CAAWBYDCGcu0S3DFeetReqfb6tV9J0eQay9M3tE=NeKSLTmL8Nw@mail.gmail.com Response: https://www.w3.org/mid/CAFDDJ7wQ77_q23i3vJJmGubM6jBiCkbgR3QJcS6VRQk0H0C=kQ@mail.gmail.com Response: https://www.w3.org/mid/C095D0EA-9473-4F5C-9E2A-8F7550F31A01@me.com Response: https://www.w3.org/mid/56C7D1B2.4030700@inkedblade.net Open: Rejected? Resolved: =WG= Discuss.
Issue 50. # Summary: Some cubic-bezier functions output out of range [0,1] From: hiikezoe Comment: https://github.com/w3c/csswg-drafts/issues/744 Response: Open: =ED= Solve or agenda+. Resolved:
Issue 51. # Summary: scale 0 on non-scaling stroke From: Rik Cabanier Comment: http://www.w3.org/mid/CAGN7qDB29wTjx0KVOjpozGckXRevZ-JVkDnFTh1-+1v9FDkEiw@mail.gmail.com Comment: http://www.w3.org/mid/201205121352.41569.Dr.O.Hoffmann@gmx.de Response: https://github.com/w3c/csswg-drafts/issues/929 Response: Open: ? Resolved: ?
Issue 52. # Summary: Some comments on the non-scaling stroke spec text From: Dr. Olaf Hoffman Comment: http://www.w3.org/mid/201205132051.25760.Dr.O.Hoffmann@gmx.de Comment: https://github.com/w3c/csswg-drafts/issues/930 Open: =ED= Edit, file issues, or close as necessary. Resolved: Editor discretion
Issue 53. # Summary: skew() is messed up From: Dr. Olaf Hoffman Comment: http://www.w3.org/mid/201203071410.51426.Dr.O.Hoffmann@gmx.de Comment: http://www.w3.org/mid/C4ADC064-7771-483F-AF81-79D6D54671B4@adobe.com Response: https://github.com/w3c/csswg-drafts/issues/931 Open: =WG= Discuss.
Issue 54. # Summary: Rendering transforms with non-invertible matrix From: Dr. Olaf Hoffman Comment: http://www.w3.org/mid/201204221814.06054.Dr.O.Hoffmann@gmx.de Response: https://github.com/w3c/csswg-drafts/issues/930 Open: =ED= Figure out issue. =WG= Discuss & resolve.
Issue 55. # Summary: animateTransform thread of unclear conclusion From: Dr. Olaf Hoffmann Comment: http://www.w3.org/mid/201204261843.03940.Dr.O.Hoffmann@gmx.de Continue: http://www.w3.org/mid/C3DB860D-28F2-4388-9D9E-513597FFAFE4@adobe.com Open: =SVGWG= Figure out if this thread is 100% handled Resolved:
Issue 56. # Summary: Deprecate animateTransform From: Dr. Olaf Hoffman Comment: http://www.w3.org/mid/86583EBE-30F0-41BD-B3E2-E6D5588BB821@adobe.com Open: =SVGWG= Figure this out and respond to thread. Resolved:
Issue 57. # Summary: Neutral element for addition wrt animating transforms From: Dirk Schulze Comment: http://www.w3.org/mid/24BE3FE7-60C9-4690-A01C-F2291460DE7F@adobe.com Response: https://github.com/w3c/csswg-drafts/issues/932 Open: =WG=/=SVGWG= Discuss.
Issue 58. # Summary: Transforms vs background-attachment: fixed From: Simon Fraser Comment: http://www.w3.org/mid/42ED583F-AFF2-4D49-B20A-4335C93EEA23@me.com Response: http://www.w3.org/mid/op.wgl87egg4p7avi@localhost.localdomain Comment: http://www.w3.org/mid/CAKA+AxnmG8CynocjdOQR-6WrZDa-uGwGpO74KUMBo0W2x8waWA@mail.gmail.com Notes: https://www.w3.org/Bugs/Public/show_bug.cgi?id=15833 Response: https://github.com/w3c/csswg-drafts/issues/933 Response: Open: =WG= Discuss.
Issue 59. # Summary: Use 'will-change' to optimize rasterization From: chrishtr Comment: https://github.com/w3c/csswg-drafts/issues/236 Response: Changes: Open: =WG= Discuss. Resolved:
Issue 60. # Summary: matrix() and matrix3d() should be same primitive From: Comment: https://lists.w3.org/Archives/Public/www-style/2017Feb/0048.html Open: =ED= Edit. Resolved: https://lists.w3.org/Archives/Public/www-style/2017Feb/0048.html