You have to start testing your product ;), browsing the web with opened console and watching torbutton's INFOs in different circumstances. You don't like similar, but separate issues in one ticket, so some of them are in other tickets, blogs, remarks - all tests for "previous version" of FPI are also actionable. Why didn't you test Mozilla's FPI as yours - that's the question.
You have to start testing your product ;), browsing the web with opened console and watching torbutton's INFOs in different circumstances.
I am doing that for weeks now. If you file a bug just dropping that log snippet into the description as you did what are we supposed to do with it? And how are we supposed to deal with "and many, many others..." in this bug?
So, again, how can I reproduce the problem you reported?
You have to start testing your product ;), browsing the web with opened console and watching torbutton's INFOs in different circumstances.
I am doing that for weeks now.
And? Don't you see FPI violations (except for retrying downloads)?
If you file a bug just dropping that log snippet into the description as you did what are we supposed to do with it?
Maybe, fix it? No?
And how are we supposed to deal with "and many, many others..." in this bug?
Make this ticket parent for all regressions in FPI?
So, again, how can I reproduce the problem you reported?
Open http://hpr.dogphilosophy.net/test on Medium settings (notice that DevTools suxx too), click "(click to try it)" near ""wave" file(".wav")". Isn't it easy?
You have to start testing your product ;), browsing the web with opened console and watching torbutton's INFOs in different circumstances.
I am doing that for weeks now.
And? Don't you see FPI violations (except for retrying downloads)?
If you file a bug just dropping that log snippet into the description as you did what are we supposed to do with it?
Maybe, fix it? No?
And how are we supposed to deal with "and many, many others..." in this bug?
Make this ticket parent for all regressions in FPI?
This is no regression, see below. But that said #20685 (moved) seems to be the parent ticket you are looking for (in case there isn't already a more specific fitting your bug). Feel free to open child tickets for issues you find with steps to reproduce them. Thanks.
So, again, how can I reproduce the problem you reported?
Open http://hpr.dogphilosophy.net/test on Medium settings (notice that DevTools suxx too), click "(click to try it)" near ""wave" file(".wav")". Isn't it easy?
Yes, with steps to reproduce it is. FWIW: I see this in 6.5.2 as well, so this has nothing to do with Mozilla's First Party Isolation code.
Trac: Priority: Medium to High Summary: Mozilla's FPI suxx to Triggering the external helper dialog leads sometimes to requests going over the catch-all circuit
This is no regression, see below. But that said #20685 (moved) seems to be the parent ticket you are looking for (in case there isn't already a more specific fitting your bug). Feel free to open child tickets for issues you find with steps to reproduce them. Thanks.
I didn't write it's a regression. But you don't mind that Mozilla's FPI suxx, right? You just didn't analyze it yet, according to #20685 (moved).
FWIW: I see this in 6.5.2 as well, so this has nothing to do with Mozilla's First Party Isolation code.
And why is ext helper triggered here instead of playing wav in the browser (as others)?