home.social

#webinspector — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #webinspector, aggregated by home.social.

  1. RE: mastodon.social/@eurozerozero/

    It has taken years and several attempts, but it looks like this bug with Safari’s Web Inspector (which I would run into every day!) might now actually be fixed in Safari Technology Preview 243. Here’s the commit that also details the race condition that caused it:

    github.com/WebKit/WebKit/commi

    FB11886541 ✅

    #WebInspector #Safari #SafariTechnologyPreview #WebKit #FeedbackAssistant

  2. RE: mastodon.social/@eurozerozero/

    It has taken years and several attempts, but it looks like this bug with Safari’s Web Inspector (which I would run into every day!) might now actually be fixed in Safari Technology Preview 243. Here’s the commit that also details the race condition that caused it:

    github.com/WebKit/WebKit/commi

    FB11886541 ✅

    #WebInspector #Safari #SafariTechnologyPreview #WebKit #FeedbackAssistant

  3. RE: mastodon.social/@eurozerozero/

    It has taken years and several attempts, but it looks like this bug with Safari’s Web Inspector (which I would run into every day!) might now actually be fixed in Safari Technology Preview 243. Here’s the commit that also details the race condition that caused it:

    github.com/WebKit/WebKit/commi

    FB11886541 ✅

    #WebInspector #Safari #SafariTechnologyPreview #WebKit #FeedbackAssistant

  4. RE: mastodon.social/@eurozerozero/

    It has taken years and several attempts, but it looks like this bug with Safari’s Web Inspector (which I would run into every day!) might now actually be fixed in Safari Technology Preview 243. Here’s the commit that also details the race condition that caused it:

    github.com/WebKit/WebKit/commi

    FB11886541 ✅

    #WebInspector #Safari #SafariTechnologyPreview #WebKit #FeedbackAssistant

  5. Also, does the Safari Web Inspector not understand nested CSS syntax, or is the red syntax highlighting colour an intentional choice for nested rules? Because having this displayed in red sure suggests that it’s invalid syntax.

    (I can only assume it doesn’t understand nesting because there’s also no way to edit nested rules directly in the Styles pane of the Elements tab)

    WebKit/Safari team: FB21689793

    #WebKit #Safari #CSS #WebInspector #FeedbackAssistant

  6. Also, does the Safari Web Inspector not understand nested CSS syntax, or is the red syntax highlighting colour an intentional choice for nested rules? Because having this displayed in red sure suggests that it’s invalid syntax.

    (I can only assume it doesn’t understand nesting because there’s also no way to edit nested rules directly in the Styles pane of the Elements tab)

    WebKit/Safari team: FB21689793

    #WebKit #Safari #CSS #WebInspector #FeedbackAssistant

  7. Also, does the Safari Web Inspector not understand nested CSS syntax, or is the red syntax highlighting colour an intentional choice for nested rules? Because having this displayed in red sure suggests that it’s invalid syntax.

    (I can only assume it doesn’t understand nesting because there’s also no way to edit nested rules directly in the Styles pane of the Elements tab)

    WebKit/Safari team: FB21689793

    #WebKit #Safari #CSS #WebInspector #FeedbackAssistant

  8. Also, does the Safari Web Inspector not understand nested CSS syntax, or is the red syntax highlighting colour an intentional choice for nested rules? Because having this displayed in red sure suggests that it’s invalid syntax.

    (I can only assume it doesn’t understand nesting because there’s also no way to edit nested rules directly in the Styles pane of the Elements tab)

    WebKit/Safari team: FB21689793

    #WebKit #Safari #CSS #WebInspector #FeedbackAssistant

  9. While working with the dialog element over the past week I keep seeing this Safari Web Inspector bug:

    Having a nested @ starting-style rule within dialog::backdrop causes the Web Inspector to display the wrong style definitions when inspecting elements within a dialog element.

    e.g. inspecting a button inside a form in the dialog shows the form’s styles as the button’s styles, an off-by-one type bug.

    WebKit/Safari team: FB21689457

    #WebKit #Safari #CSS #WebInspector #FeedbackAssistant

  10. While working with the dialog element over the past week I keep seeing this Safari Web Inspector bug:

    Having a nested @ starting-style rule within dialog::backdrop causes the Web Inspector to display the wrong style definitions when inspecting elements within a dialog element.

    e.g. inspecting a button inside a form in the dialog shows the form’s styles as the button’s styles, an off-by-one type bug.

    WebKit/Safari team: FB21689457

    #WebKit #Safari #CSS #WebInspector #FeedbackAssistant

  11. While working with the dialog element over the past week I keep seeing this Safari Web Inspector bug:

    Having a nested @ starting-style rule within dialog::backdrop causes the Web Inspector to display the wrong style definitions when inspecting elements within a dialog element.

    e.g. inspecting a button inside a form in the dialog shows the form’s styles as the button’s styles, an off-by-one type bug.

    WebKit/Safari team: FB21689457

    #WebKit #Safari #CSS #WebInspector #FeedbackAssistant

  12. While working with the dialog element over the past week I keep seeing this Safari Web Inspector bug:

    Having a nested @ starting-style rule within dialog::backdrop causes the Web Inspector to display the wrong style definitions when inspecting elements within a dialog element.

    e.g. inspecting a button inside a form in the dialog shows the form’s styles as the button’s styles, an off-by-one type bug.

    WebKit/Safari team: FB21689457

    #WebKit #Safari #CSS #WebInspector #FeedbackAssistant

  13. Hmm, it seems the Web Inspector in Safari (including in Safari Technology Preview) doesn’t know about the hanging and each-line keywords of the text-indent property.

    Instead, it still lists -webkit-each-line and -webkit-hanging, neither of which actually even works now.

    Maybe it never got updated when Safari started supporting the unprefixed versions?

    Also, Firefox finally supports these keywords (since December), but Chrome still doesn’t!

    #Safari #SafariTechnologyPreview #STP #WebInspector

  14. Hmm, it seems the Web Inspector in Safari (including in Safari Technology Preview) doesn’t know about the hanging and each-line keywords of the text-indent property.

    Instead, it still lists -webkit-each-line and -webkit-hanging, neither of which actually even works now.

    Maybe it never got updated when Safari started supporting the unprefixed versions?

    Also, Firefox finally supports these keywords (since December), but Chrome still doesn’t!

    #Safari #SafariTechnologyPreview #STP #WebInspector

  15. Hmm, it seems the Web Inspector in Safari (including in Safari Technology Preview) doesn’t know about the hanging and each-line keywords of the text-indent property.

    Instead, it still lists -webkit-each-line and -webkit-hanging, neither of which actually even works now.

    Maybe it never got updated when Safari started supporting the unprefixed versions?

    Also, Firefox finally supports these keywords (since December), but Chrome still doesn’t!

    #Safari #SafariTechnologyPreview #STP #WebInspector

  16. Hmm, it seems the Web Inspector in Safari (including in Safari Technology Preview) doesn’t know about the hanging and each-line keywords of the text-indent property.

    Instead, it still lists -webkit-each-line and -webkit-hanging, neither of which actually even works now.

    Maybe it never got updated when Safari started supporting the unprefixed versions?

    Also, Firefox finally supports these keywords (since December), but Chrome still doesn’t!

    #Safari #SafariTechnologyPreview #STP #WebInspector

  17. Hmm, it seems the Web Inspector in Safari (including in Safari Technology Preview) doesn’t know about the hanging and each-line keywords of the text-indent property.

    Instead, it still lists -webkit-each-line and -webkit-hanging, neither of which actually even works now.

    Maybe it never got updated when Safari started supporting the unprefixed versions?

    Also, Firefox finally supports these keywords (since December), but Chrome still doesn’t!

    #Safari #SafariTechnologyPreview #STP #WebInspector

  18. @jensimmons excited to see the updates for #WebInspector and #visionOS. I use inspector daily in my work and I’m curious about web design and W3C standards for special computing web sites.

  19. @jensimmons excited to see the updates for and . I use inspector daily in my work and I’m curious about web design and W3C standards for special computing web sites.

  20. @jensimmons excited to see the updates for #WebInspector and #visionOS. I use inspector daily in my work and I’m curious about web design and W3C standards for special computing web sites.

  21. @jensimmons excited to see the updates for #WebInspector and #visionOS. I use inspector daily in my work and I’m curious about web design and W3C standards for special computing web sites.

  22. @jensimmons excited to see the updates for #WebInspector and #visionOS. I use inspector daily in my work and I’m curious about web design and W3C standards for special computing web sites.

  23. TIL you need to enable Safari’s Web Inspector explicitly for any WKWebView in iOS 16.4. Such fun sorting out the “No Inspectable Applications” item that shows up unexpectedly in Safari’s Develop menu.

    #swift #webKit #swiftUI #webInspector

    webkit.org/blog/13936/enabling

  24. TIL you need to enable Safari’s Web Inspector explicitly for any WKWebView in iOS 16.4. Such fun sorting out the “No Inspectable Applications” item that shows up unexpectedly in Safari’s Develop menu.

    #swift #webKit #swiftUI #webInspector

    webkit.org/blog/13936/enabling