Also when i receive a warning on the browser toolbox is there any way to know from which path it comes (I mean stack trace)?
It depends. If the warning passed an Error, then you get it for free. Otherwise, it will only show you the filename and line number where the warning was logged, and from there you could attach a breakpoint and wait to hit it again.
I would be interested in a write-up about your stream setup / equipment
Can you explain the process of writing “These Weeks in Firefox” (from start to finish) ?
https://wiki.mozilla.org/Firefox/Meeting
During the meeting, we take notes as updates are given.
After the meeting, a few of us stick around to rewrite the meeting notes into something more palatable
We put developer-centric things in “Below the fold” - this doesn’t make the cut to the blog, but goes to the firefox-dev mailing list
We then post to firefox-dev and the blog. Done!
WebExtensions and how they interact with DocShells / BrowsingContexts
Next episode. Promise.
How a patch gets into Firefox, from start to finish!
Next episode. Promise.
I have been watching your videos for about two years now. I’m curious if you know who smurfd is. Have you ever met?
No! Have never met. Don’t know where they are. Don’t know who they are. But they’re great.
And i can unfortunately not remember how or when i found JOC. I suspect it was either from planet.mozilla.org or via twitter. Always thought of it as, if you had a good tv show you could contribute to, would you not do that? /smurfd
Read anything interesting lately?
After the Flood by Margaret Atwood (MaddAddam trilogy)
Hands on Rust
Cracked the cover, started reading, looks good, haven’t gotten into the meat of it yet. Maybe over the winter holidays, when I have some real focus time.