Reviews & Comments of z-context chrome extension

From August 2nd, 2016 to March 4th, 2023, 52% user give 5-star rating, 9% user give 4-star rating, 9% user give 3-star rating, 4% user give 2-star rating, 26% user give 1-star rating. for z-context chrome extension.

Reviews of z-context:


Zachary Wiles March 4th, 2023
Zachary Wiles

I have found that z-context v2.1.0 doesn't work (empty panel) upon first install until the browser is restarted. Temp fix: restart chrome browser after install. FAQ: Where does the Z-index panel appear? On the panel row with the Styles tab, at the very end, probably need to click the disclosure >> You can then rearrange by dragging the tab left.


Lumbardh Elshani August 18th, 2022
Lumbardh Elshani

Not working


Sebastian Vittersø November 2nd, 2021
Sebastian Vittersø

Worked wonders, super helpful for solving a problem related to stacking context.


Artur Mueller Romanov August 19th, 2021
Artur Mueller Romanov

Not working in chrome 2021


Sergey Grishanin August 3rd, 2021
Sergey Grishanin

Doesn't work on latest chrome. Reloading the browser or reinstalling the extension doesn't help - the tab is always empty


Vermus August 2nd, 2021
Vermus

Not work in 2021


Ben Manson February 13th, 2020
Ben Manson

did not work, does not appear in dev tools even after restart, a how to would be nice


David Rickard October 30th, 2019
David Rickard

Thanks. Was going crazy trying to figure out why a stacking context was getting created and this one told me exactly why.


Pedro Torchio June 23rd, 2019
Pedro Torchio

Crazy useful. Can't dev Webapps without it anymore


T N June 5th, 2019
T N

could not figure out how to use if :(


Drazen Bjelovuk May 27th, 2019
Drazen Bjelovuk

Super handy.


Ivan Fedulov December 5th, 2018
Ivan Fedulov

Occurred to be very helpful when I stuck with debugging z-index issue in markup. Would be very nice if displayed properties *current* and *parentStackingContext* will point to real DOM nodes in Elements tab, not just strings with class names (which sometimes are absent when element has inline styles).


Josh Wright September 11th, 2018
Josh Wright

You have to completely restart Chrome for this extension to start working. Took me a while to figure that out.


Ben McCallum September 5th, 2018
Ben McCallum

Great to understand/debug your z-indexes and stacking contexts. Should def be in DevTools natively :) Thanks heaps.


vamshi krishna August 23rd, 2018
vamshi krishna

Could not see the tab in dev tools , even after restarting and refresh . A good how to is helpful


Ryan Karumanchery July 31st, 2018
Ryan Karumanchery

Insanely helpful. I've spent hours trying to figure out the stacking context of my elements, while this extension helped solve my problem in a few minutes.


Dmitri Pisarev December 4th, 2017
Dmitri Pisarev

This extension is very helpful. But I wasted a ton of time because of the bug in it. It reports new stacking context for any value of "will-change", even smth like "will-change: left", which obviously doesn't create a stacking context. According to the spec: "Element with a will-change value specifying any property that would create a stacking context on non-initial value"


Tristan Scaglia September 27th, 2017
Tristan Scaglia

Perfect to find out which stacking context an element belongs to.


Nils Lundquist September 15th, 2017
Nils Lundquist

awesome extension. so useful for debugging unexpected z-index behaviour.


Dmitrii June 8th, 2017
Dmitrii

Awesome: very useful for checking an element z-index


Max Dudzinski May 22nd, 2017
Max Dudzinski

Awesome extension, has helped me a lot when trying to level stacking contexts in order to display custom overlays. Light and straight to the point, with good selection of information that it makes available at a glance. Like Aviral said really surprising that its not part of CDT


Aviral Dasgupta January 17th, 2017
Aviral Dasgupta

Works well for what it does. Surprising that this isn't built into CDT already.


James Williams August 2nd, 2016
James Williams

Really handy! But why on earth does it need permissions to *change* data on websites I visit? Surely *reading* that data is enough for the current functionality?