overwriting z-index in --production
See original GitHub issueHi, i hope this is the right place to submit an issue.
after running gulp --production
sass ignores my z-index
and sets whatever it wants leads to some UX problems.
Bug found while using following stack:
- elixir
- angular
- angular material …
Issue Analytics
- State:
- Created 8 years ago
- Comments:7
Top Results From Across the Web
Managing CSS Z-Index In Large Projects - Smashing Magazine
Wrangling z-index values is a difficult task for many developers. Here is an easy-to-implement mini-framework based on existing conventions ...
Read more >issues with z-index and multiple !important rules
x-floating declaration being overwritten (crossed out), and the x-floating declaration being active. This goes against what I know of css specificity, and what ......
Read more >Z-index and stacking contexts - web.dev
In this module find out how to control the order in which things layer on top of each other, by using z-index and...
Read more > How to solve the Z-index issue Within 1 minute - DEV ...
The z-index in html overrides the the natural order in the Dom. The primary method for getting things to show up should always...
Read more >The CSS z-index Property: What You Need to Know
In this example, we use z-index to override the default stacking. Now, the first written div (“first”) is at the top of the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Turns out this occurs if you use cssnano in the pipe.
Using cssnano as:
.pipe(cssnano({ zindex: false }))
fixes the zindex changing.
http://cssnano.co/optimisations/#optimise-z-index-unsafe-
i will try to get more info. maybe its referencing to the elixir. but still this is very strange.
every time i set f.i.
.some-class { z-index: 99 }
after gulp in production i seez-index: 19
or 18. like sass was trying to calculate the indexes on its own.