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

  • (no subject)

    On the dreadful state of the style of modern Russian communication. "There is no alternative", writes an author, and then immediately outlines an…

  • Via Twitter

    Via a tweet, but I thought I'd get my own copy. A beautiful illustration of how a caption totally misrepresents what's been captured in the photo.…

  • (no subject)

    Here's an extract from Uncle Bob's book Clean Agile. Although he has fallen out of grace with the champions of social justice, the sentiment…

  • 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