HNHacker News
TopNewBestAskShowJobs

digitarald

112 karma · joined December 13, 2011

Globetrotting Web Craftsman. Crafting poetic web code and functional interfaces since 1999. Fighting for the good of the Web with Mozilla.
submissionscomments
digitarald··on Firefox 73
Firefox dev here – do you have an example page? We worked a lot on source maps, so things should have improved but maybe you hit a regression.
digitarald··on Firefox 73
That is on our list for sure and some fixes have landed in 74 and 75. More to do for sure, but these issues are a priority in our performance program.

> then manually kill the Chrome tab and I can still run through 1 million console lines smoothly

How does that work with DevTools – closing the tab and reading logs?

digitarald··on Firefox 73
Text input is a priority but also hard to align on is complex, potentially risky, work.

Console log background was worked on by a contributor as its a good first bug.

digitarald··on Firefox 73
Firefox dev here: Just to understand the use case (and others can pile on too) – do you use Lighthouse for online staged/prod sites or local testing?
digitarald··on Firefox 73
Firefox dev here. Making sure failed requests are properly highlighted in Network panel is a big one on our list!
digitarald··on Firefox 73
I am on Nightly which updates 2x daily without problems. If restart doesn't work maybe try a re-install. Filing a bug would be great so Firefox devs can work with you to find a root cause.

On Windows it should background update now as well.

digitarald··on Firefox 73
Firefox member here – thanks a lot for reporting those bugs! Thanks to detailed reports Debugger could improve and glitches should become more and more a rarity.
digitarald··on Chrome 80 Is 30% Slower Than Chrome 75
Coming in 76/77: https://bugzilla.mozilla.org/show_bug.cgi?id=1528294
digitarald··on Chrome 80 Is 30% Slower Than Chrome 75
Please report those via webcompat.com – Firefox's compat team will always follow up and learn more how to close the platform gap that causes the issues but also reach out to the devs.
digitarald··on Chrome 80 Is 30% Slower Than Chrome 75
Wonder if Firefox works better on your projects, as a lot of work went into debugging quality and performance. Have you tried it out lately?
digitarald··on Chrome 80 Is 30% Slower Than Chrome 75
Cautious that this is just the v8 team though.
digitarald··on Firefox 72.0
Could you file an issue here? https://webcompat.com/issues/new
digitarald··on Firefox 72.0
DevTools member here. We have been working on performance over the past release – is there anything specific that you can point out as being slower for us to focus on?
digitarald··on Firefox 72.0
Thanks again for that discussion, it already spawned some follow up.
digitarald··on Firefox 72.0
DevTools member here. As this is something we are chipping away on, are there any specific places where the UI throws you off?
digitarald··on No to Chrome
~10 across various panels and the new profiler.firefox.com.
digitarald··on No to Chrome
Also, Network full-test search is now in the Network panel
digitarald··on No to Chrome
Firefox DevTools member here. If you have tried them recently, I'd love your feedback on what's blocking you.
digitarald··on No to Chrome
DevTools member here: We have a more powerful target switching (hidden) in the toolbar but are also working to better expose JS context switching early next year.

Debugger's new threads panel also solves this partially when you pause in a thread.

Are your use cases extensions, workers or iframes?

digitarald··on No to Chrome
Password generation landed in 69, right?

Latest on Keychain sopport is in https://bugzilla.mozilla.org/show_bug.cgi?id=106400#c130 as WONTFIX due to macOS changes.

digitarald··on No to Chrome
Firefox DevTools member here. We are looking into Puppeteer/CDP – what is the product you depend on? If you can't post it here, feel free to email me [nickname] at mozilla org
digitarald··on Firefox Replay
Correct on premature launch! Handling all the excitement was fun though while preparing food. There is a lot more work and research needed before rolling this out further.
digitarald··on Firefox’s New WebSocket Inspector
This would be a great feature request. Filed https://bugzilla.mozilla.org/show_bug.cgi?id=1588994
digitarald··on Firefox’s New WebSocket Inspector
We are looking into that right now actually to make that easier, maybe you could file a specific bug. Are you using the iframe-picker in Firefox and that isn't working as expected?
digitarald··on Firefox’s New WebSocket Inspector
Proper undo-redo is on the roadmap. It works in some cases but needs to work throughout the whole Inspector!
digitarald··on Firefox’s New WebSocket Inspector
Yes, this is upcoming next as binary preview is pretty bad without it.
digitarald··on Firefox’s New WebSocket Inspector
I'd love to hear what other things come to mind regarding feature parity. We have been hitting a few of those out of the park lately and are slowly running out of obvious ones crossing fingers
digitarald··on Firefox’s New WebSocket Inspector
Does that bug I filed capture it? https://bugzilla.mozilla.org/show_bug.cgi?id=1567606
digitarald··on Firefox’s New WebSocket Inspector
It does seem nice to at least know when messages were sent/received in context, while not killing the performance of the network tab. I filed it as a feature request: https://bugzilla.mozilla.org/show_bug.cgi?id=1588859
digitarald··on Firefox’s New WebSocket Inspector
We have them in the backlog and had some conversations with users about them to scope them out. What are you using them for? We hear it a lot from the ClojureScript community.
Page 1 of 2Next →