3 ms·
FF and Safari are both shipping some great stuff that we don't have in Chrome DevTools. Canvas debugger: https://webkit.org/blog/8452/canvas-debugging/ https:/
by kaycebasques 7y ago
FF and Safari are both shipping some great stuff that we don't have in Chrome DevTools.
Canvas debugger: https://webkit.org/blog/8452/canvas-debugging/ https://webkit.org/blog/8452/canvas-debugging/
Flexbox inspector: https://developer.mozilla.org/en-US/docs/Tools/Page_Inspector/How_to/Examine_Flexbox_layouts https://developer.mozilla.org/en-US/docs/Tools/Page_Inspecto...
Fonts tab: https://developer.mozilla.org/en-US/docs/Tools/Page_Inspector/How_to/Edit_fonts https://developer.mozilla.org/en-US/docs/Tools/Page_Inspecto...
- kaycebasques 7y agoAlso: > everything moving to Chromium... [including] Safari This is the opposite of true
- tty2300 7y agoWhen will safari provide a VM image so developers can actually test things on it?
- pwdisswordfish2 7y agoWhy would you need to? Just test things on another WebKit browser, it will work just as well on Safari.
- javagram 7y agoWhat actively-developed WebKit browsers still exist for Windows? FWIW, the assumption that safari and some random WebKit browser will behave the same seems unsafe to me. The release version of safari will probably be on a newer/older WebKit edition and stuff like tracking protection might behave differently.
- zachwood 7y agoThat's got nothing to do with Chromium becoming ubiquitous as far as market share goes. Which is bad for everyone.
- kaycebasques 7y agoSorry, given that this is a thread about DevTools I thought the conversation was scoped to DevTools. Didn't realize we were talking about browser share at large.