Andrey (azangru) wrote,
Andrey
azangru

Another example of when developing/debugging experience with Firefox is unexpectedly superior to Chrome.

Playing with a custom element that doesn't want to change its height. Tried the percentages first, then capitulated and tried an arbitrary absolute value in pixels, but the stubborn custom element wouldn't budge. Staring stupidly at Chrome dev tools:



Why, why wouldn't you change your height, you little piece of shit? Have I mistyped the word height? Did I forget some fundamental truth about custom elements? Have I gone mad? Has Chrome gone mad? Only one way to test the latter...

...opens in Firefox...

Oh! Oh look, the height is all greyed out, and there is an info button next to it. It's trying to tell me something:



Ohhhh...



Oh, custom elements have display inline by default. How silly of me. Chrome could have told me this too, right? It could have. But it didn't.
Subscribe

Recent Posts from This Journal

  • (no subject)

    A pager on the site of the Smashing Magazine: What happens when you press on the button with an ellipsis? Nothing does. Why, then, does it look…

  • (no subject)

    Glimpsed an interesting text on Facebook. Is opens a window into a consciousness that is reflecting both on the history of the Internet and on its…

  • (no subject)

    They are both developer advocates. And they both talk about the Chrome 90 release. But they have different linguistic proficiency. Compare and…

  • Post a new comment

    Error

    default userpic
    When you submit the form an invisible reCAPTCHA check will be performed.
    You must follow the Privacy Policy and Google Terms of use.
  • 0 comments