| Commit message (Collapse) | Author | Age |
|
|
|
| |
This reverts commit 85dc118aaca8446cbe33671446ac23147daec44c.
|
| |
|
|
|
|
| |
While we do fail a couple of tests, the other mainstream browsers also fail them and I think our implementation of tab-size is good enough to be unprefixed at this point. Having this patch also makes testing easier.
|
|
|
|
|
|
|
|
| |
This actually keeps both pseudo-elements for now, since the prefixed version is
still used internally, but we need the unprefixed version for web compat.
Note: while unprefixing a non-spec-compliant pseudo here, it's exactly in line
with what other browsers do. Nobody is following the spec here and at least
we'll be doing what everyone else is with our unprefixed version.
|
|
|
|
|
|
| |
This CSS property allows input carets (that blinking input cursor you see in text fields), to be given a custom color. This was implemented in Firefox 53, and it was such a minor feature that no one ever missed it, but I don't see any harm in implementing this.
https://bugzilla.mozilla.org/show_bug.cgi?id=1063162
|
|
|
|
| |
Tag #1666
|
|
|
|
|
| |
This reverts commit ed88b99849156004c04e4a0c87ea9b2360ef19b6, reversing
changes made to c4b0715baaffc541670fd1158557aa7e61e521d3.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
DevTools
I am so done with this.
Resolves #316
|
|
|
|
| |
This resolves Issue #316
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
This removes a ton of tests that are no longer relevant with (un)watch
removed (e.g. testing stability/bugs in the watchpoint system itself
which has never been the most stable), and updates others that would
previously rely on watch/unwatch, so that they don't unexpectedly fail.
|
|
|
|
|
| |
Ref:
1398537 part 4 - [css-multicol] Implement percentages for 'column-gap' (automated update of devtools).
|
|
|
|
| |
Removes all occurrences of MOZ_DEV_EDITION code and some helpers.
|
|
|
|
| |
Follow-up to issue #1138.
|
|
|
|
|
|
| |
Saving JSON from the viewer was broken, because the message passed to
the `saveToFile` function contained unneeded data. This bug was
introduced by 23e68227a2e3f3946fa4fd5589f338e6b36a6e56.
|
|
|
|
| |
Mozilla Bug 1368899
|
|
|
|
| |
Mozilla Bug 1395313
|
|
|
|
| |
Mozilla Bug 1367894
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
This resolves #1123
|
|
|
|
| |
MOZ_FENNEC
|
| |
|
| |
|
| |
|
|\ |
|
| |\
| | |
| | | |
Issue #756 - Remove Contextual Identity
|
| | | |
|
| |/ |
|
| | |
|
| |
| |
| |
| |
| |
| | |
- Conditional code
- WE APIs
- WE toolkit theming
|
| | |
|
|/ |
|
| |
|
|
|
|
| |
Tag #21.
|
|\
| |
| | |
Issue #792 - backport mozbug 1334776 - CVE-2017-7797 Header name interning leaks across origins
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
origins
Potential attack: session supercookie.
[Moz Notes](https://bugzilla.mozilla.org/show_bug.cgi?id=1334776#c5):
"The problem is that for unknown header names we store the first one we see and then later we case-insensitively match against that name *globally*. That means you can track if a user agent has already seen a certain header name used (by using a different casing and observing whether it gets normalized). This would allow you to see if a user has used a sensitive service that uses custom header names, or allows you to track a user across sites, by teaching the browser about a certain header case once and then observing if different casings get normalized to that.
What we should do instead is only store the casing for a header name for each header list and not globally. That way it only leaks where it's expected (and necessary) to leak."
[Moz fix note](https://bugzilla.mozilla.org/show_bug.cgi?id=1334776#c8):
"nsHttpAtom now holds the old nsHttpAtom and a string that is case sensitive (only for not standard headers).
So nsHttpAtom holds a pointer to a header name. (header names are store on a static structure). This is how it used to be. I left that part the same but added a nsCString which holds a string that was used to resoled the header name. So when we parse headers we call ResolveHeader with a char*. If it is a new header name the char* will be stored in a HttpHeapAtom, nsHttpAtom::_val will point to HttpHeapAtom::value and the same strings will be stored in mLocalCaseSensitiveHeader. For the first resolve request they will be the same but for the following maybe not. At the end this nsHttpAtom will be stored in nsHttpHeaderArray. For all operation we will used the old char* except when we are returning it to a script using VisitHeaders."
|
|/ |
|
|
|
|
|
| |
This creates a number of stubs and leaves some surrounding code that may be irrelevant (eg. recorded time stamps, status variables).
Stub resolution/removal should be a follow-up to this.
|