|
@addyosmani | |||||
|
Tip: @ChromeDevTools has a Shadow Editor built in! pic.twitter.com/NptZeGQWTy
|
||||||
|
||||||
|
Kevin Lozandier
@KevinLozandier
|
29. sij |
|
Is there a particular reason Chrome doesn’t have one for the more performant version, `filter: drop-shadow()`?
|
||
|
|
||
|
Addy Osmani
@addyosmani
|
29. sij |
|
I wonder if the existing editor could be expanded to support `filter`. Would you like to submit a FR via crbug.com for it?
|
||
|
|
||
|
Emma Bostian 🐞
@EmmaBostian
|
29. sij |
|
WAT
|
||
|
|
||
|
Addy Osmani
@addyosmani
|
29. sij |
|
Also works kinda nice on text shadows :) pic.twitter.com/KPNJMTWQf4
|
||
|
|
||
|
Jamie Birch
@LinguaBrowse
|
29. sij |
|
Is there a standards group for browser dev tools? I keep seeing nice features being added exclusively by each different browser (e.g. @WebKit added editing of remote scripts, @FirefoxDevTools added the Flexbox inspector) – why can't we all have the same things? 😅
|
||
|
|
||
|
𝕡𝕒𝕥𝕣𝕚𝕔𝕜
@patrickbrosset
|
29. sij |
|
It would be great. Unfortunately this does not exist. DevTools are, currently, a way in which browser vendors friendly compete against each other, and the features that come up are often a result of each vendor's strategy and technical capability.
|
||
|
|
||
|
Brian Belhumeur
@JSArtisan
|
29. sij |
|
Ah this is so much nicer than using up and down arrow keys trying to remember the order of the four arguments (was spread the third, or the fourth?). Beautiful!
|
||
|
|
||
|
Yasin Eksi
@yasinfb1907
|
29. sij |
|
Yeah! That’s good to know. No more searching a page with a generator :)
|
||
|
|
||
|
Mattia Astorino
@equinusocio
|
29. sij |
|
We need a CSS filter editor too!
|
||
|
|
||
|
Marvin Rudolph
@MarvinRudolph8
|
29. sij |
|
I know. That's how I have built my shadow DOM.
|
||
|
|
||