Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • B bootstrap
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 263
    • Issues 263
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 114
    • Merge requests 114
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Bootstrap
  • bootstrap
  • Issues
  • #13562
Closed
Open
Issue created May 11, 2014 by Administrator@rootContributor

skew() is apparently legacy and our -ms variant might be wrong

Created by: cvrebert

Regarding https://github.com/twbs/bootstrap/blob/82e2f87363d960b647bc1e97bf53bbb229b0e703/less/mixins/vendor-prefixes.less#L133

We're currently using transform: skew(@x, @y);. According to MDN (emphasis mine):

Note: The skew() function was present in early drafts. It has been removed but is still present in some implementations. Do not use it.

Similarly, the current spec says (emphasis mine):

Note that the behavior of skew() is different from multiplying skewX() with skewY(). Implementations must support this function for compatibility with legacy content.

So, I'm thinking that we should stop using skew(x, y)?

Relatedly, we're currently using -ms-transform: skewX(@x) skewY(@y), which based on that spec note sounds like it might not be the correct equivalent. Some testing is probably warranted.

Assignee
Assign to
Time tracking