| Commit message (Collapse) | Author | Age |
| ... | |
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| |/ |
|
| | |
|
| |
|
|
|
| |
FF2.0 is no longer supported, and this cuts a lot of exception noise out of
the javascript debugger.
|
| |
|
|
| |
This is the new official way of clearing SSL Session IDs and other TLS state.
|
| |
|
|
|
|
|
| |
Fixing these will be too problematic for 1.4.x. We'll block on this bug
forever otherwise. We throw an unknown protocol exception if this pref is set
to prevent fingerprinting with this technique:
http://pseudo-flaw.net/tor/torbutton/scan-protocol-handlers.html
|
| | |
|
| |
|
|
| |
Might end up useful in the future though.
|
| |
|
|
|
|
|
|
|
|
| |
This may not be the final form we want for it to take, see FIXME in the
comments.
Also fix a potential issue with unescaped .'s in regex match strings. I'm
really not sure we can call this ref spoofing protection a real security
feature, though, so it's not like this matters a whole bunch. But might as
well fix it, too.
|
| |
|
|
| |
Allow content sourcing of resource urls with a host of 'gre'.
|
| |
|
|
|
| |
The javascript hooks work again, and we've removed a nasty popup exception on
FF4.0b11 too.
|
| |
|
|
|
|
| |
Hopefully this does not cause us to opt-out of updates as well. That seems to
be a different pref, however:
http://kb.mozillazine.org/Updating_extensions#Disabling_update_checks_for_individual_add-ons_-_Advanced_users
|
| |
|
|
|
| |
I couldn't reproduce the issue with this fix, but reproduction seems random
and erratic, so maybe it is not fixed still..
|
| | |
|
| | |
|
| |
|
|
|
| |
We always ask this to intl users, because really it's quite fair for them to
choose either option, depending on their use case.
|
| | |
|
| |
|
|
|
| |
This doesn't fix the root issue of our JS hooks being broken, but that has
existed since at least FF4.0b8. See #2465 for that issue.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
All languages were carefully edited but the zh-CN one I left apart since it did
not seem a trivial replacement to do.
|
| | |
|
| |
|
|
|
|
| |
FF4 disables the addon-bar, which somehow propagates immutable invisibility
status to the context menu there, so we move it to the nav-bar instead. That
was a fun one to diagnose.
|
| |
|
|
| |
FF4 breaks how this event is delivered.
|
| | |
|
| |
|
|
| |
Gotta love backwards-incompatible changes.
|
| |
|
|
| |
Eliminates weird behaviors for updating addons.
|
| |
|
|
| |
They were too complicated and confusing. Lets just make it simple.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Was missing some events.
|
| |
|
|
|
|
| |
Hopefully this will help cut down on mode error. Oddly enough, found a FF4
toolbar button issue related to a TabOpen event getting registered too early.
Possibly also solves bug #1392 and #992?
|
| | |
|
| |
|
|
|
|
| |
This now involves only keeping places.history.enabled in sync with our prefs.
The CSS history attack is now fixed in FF4, so we do not need to pay attention
to the read pref.
|
| | |
|
| |
|
|
|
|
|
|
| |
We now filter the JSON data written to the store instead of reimplementing the
component used to create it. This is slightly less fragile than what we used
to do, but perhaps not by much. If the structure of the session store changes
substantially, we'll break. From the comments, it does look like they try to
keep some level of compatibility with previous formats..
|
| | |
|
| | |
|
| |
|
|
|
| |
Also simplify it. There's no real reason for it to hook the SessionRestore
component. We will handle that via observer topics in a different component.
|
| |
|
|
|
| |
Don't touch gopher settings for FF4. gopher support has finally been removed.
RIP, archie. No one will miss you.
|
| | |
|
| | |
|