Yes, this is really helpful
In Firefox 63 (currently Nightly, next week in Beta), Error messages are more detailed when accessing a property on an undefined or null variable.
Should make it easier to find out what's wrong in a script 
Thanks @arai_unmht for this !
— @nicolaschevobbepic.twitter.com/TIJGbcATnf
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Finally!
Can't help but think the verbiage could be better, though.
- Can't access property "y" of null/undefined "x"
- "x" is null/undefined, can't access property "x.y" -
I filed https://bugzilla.mozilla.org/show_bug.cgi?id=1488417 … to make the message better. Thanks for the suggestions
End of conversation
New conversation -
-
-
FF dev tools getting better and better every iteration. I've already weaned myself off of Chrome for dev because of improvements. Keep it up! (and please can we have resizable columns in dev tools? so annoying that I can't see the info I want to see, eg on network tab)
-
Thanks for the kudos, the team is rocking it! Resizable network columns will be worked on soon, they are high in the backlog as productivity papercut. Keep the feedback coming!
- Show replies
New conversation -
-
-
-
Hello Sivan, I think you misunderstood the original intent of the tweet. Those error are made on purpose to show how the error message evolved in the last version of Firefox :)
End of conversation
New conversation -
-
-
that is one of those many simple quality of life improvements that make firefox a top tier developer experience
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.