| Commit message (Collapse) | Author | Age |
| |
|
|
|
|
|
|
| |
keyword table
This prevents the parser from accepting values outside the keyword table.
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* master:
No issue - Update README and SECURITY
Issue #1885 - Follow-up: Update error message if invalid rootMargin specified.
Issue #1879 - Follow-up: Update config/external/nss/target to security/target.
Issue #1885 - Allow unitless rootMargin entries for IntersectionObserver.
Issue #1879 - Revert changes to cryptox.h
Revert "Issue #1879 - spot-fix typo in cryptox.h"
Issue #1879 - spot-fix typo in cryptox.h
Issue #21 - Change MappedAttrParser to store its nsIPrincipal instead of nsSVGElement
Issue #21 - Remove use counters telemetry
Issue #1881 - Interpret empty or whitespace root margin string as zero length
Issue #1877 - Resolve NIGHTLY_BUILD conditionals.
Issue #1880 - Boot Comic Sans out of the font configuration.
|
| |\
| | |
| | |
| | |
| | |
| | | |
FranklinDM/UXP-contrib:work_telemetry-use-counters-removal into master
Reviewed-on: https://repo.palemoon.org/MoonchildProductions/UXP/pulls/1883
|
| | |
| | |
| | |
| | |
| | |
| | | |
This reverts Bug 968923 - Implement some equivalent of Chrome's use counters (on top of telemetry?)
For reference: https://bugzilla.mozilla.org/show_bug.cgi?id=968923
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
I could have done this through a CSSLoader to allow all CSS unit quirks but
I wasn't planning to start passing around document and element references
everywhere, so instead just did it manually by accepting numbers/floats in
addition to pixel and percent.
|
| |/
| |
| |
| |
| |
| |
| |
| | |
This attempts to get the first non-whitespace token, which if exists, continues with previous behavior of parsing the margin string. Otherwise, if the specified margin string is empty or consists only of whitespace characters, is interpreted as zero length.
IntersectionObserver is the only consumer of the `ParseMarginString` method, as far as I can tell, so this should not affect anything else.
Note: For some reason, Firefox and Chrome treat the unitless zero length as invalid, while with this change, we do not change existing behavior in that regard and continue to accept that value.
|
| | |
|
|/
|
|
| |
This reverts commit aa0fd3d68c856504646e1d7eb499bc890ef44101.
|
|
|
|
| |
tests.
|
| |
|
|
|
|
| |
fixed up.
|
|
|
|
| |
This also fixes crashing when using the grid shorthand property.
|
| |
|
| |
|
|
|
|
| |
Partially based on https://bugzilla.mozilla.org/show_bug.cgi?id=1105111
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
properties
This removes the `grid` prefix from the gap-related properties of grid since they are now part of the box alignment specification. Former grid-gap* properties were aliased to the unprefixed properties to maintain compatibility.
The previously multi-column layout only `column-gap` property has been modified to apply to the Grid layout (and Flexbox in a following commit), moving the `mColumnGap` member variable from `nsStyleColumn` to `nsStylePosition`.
Notes:
* Bug 1398537 - support for percent values in column-gap for multi-column layout landed as part of Issue #1230. However, it was incomplete because it did not update `nsRuleNode` to allow transformation of percentage values for `column-gap`. This was consequently fixed as part of this commit.
* Bug 1456166 - this might not apply because we don't have that devtools test in UXP
* `nsRuleNode`, `nsCSSParser`, `Declaration`, and other related classes were merged into Stylo. These should be taken into consideration when porting patches from Mozilla.
Partially based on https://bugzilla.mozilla.org/show_bug.cgi?id=1398482
|
|
|
|
| |
Based on https://bugzilla.mozilla.org/show_bug.cgi?id=1398492
|
|
|
|
|
| |
Note this won't give working applications. Requires FE changes and
additional js module changes (next part).
|
|
|
|
|
| |
This removes NS_ERROR_{TRACKING|MALWARE|PHISHING|UNWANTED|BLOCKED}_URI
that are no longer in use.
|
|
|
|
| |
helper functions.
|
| |
|
| |
|
|
|
|
| |
to follow it.
|
|\
| |
| |
| |
| |
| | |
stylesheets' (#1785) from athenian200/UXP:bool-chrome-stylesheets into master
Reviewed-on: https://repo.palemoon.org/MoonchildProductions/UXP/pulls/1785
|
| |
| |
| |
| | |
This functionality was already added to Gecko for UA stylesheets allow the "dom.details_element.enabled" preference to work. I changed the condition to allow bool preferences to be used in chrome stylesheets as well.
|
| |
| |
| |
| |
| | |
These are obsolete system themes; the platform will fall back to generic/unknown
theme support instead.
|
| |
| |
| |
| | |
Since we have calc() and floats working now, this is a trivial fix.
|
| |
| |
| |
| |
| | |
This adds basic calc() support to stroke-dashoffset. It does not provide
CSS animation (yet, todo for part 2)
|
|/ |
|
|\
| |
| |
| |
| |
| | |
(#1758) from athenian200/UXP:details_element_pref into master
Reviewed-on: https://repo.palemoon.org/MoonchildProductions/UXP/pulls/1758
|
| |
| |
| |
| | |
The removal of this preference was botched, all other surrounding plumbing changes appear to be working okay. The ability to use prefs to control this stylesheet might be useful in the future, so perhaps this is one of those "if it ain't broke, don't fix it" bugs where leaving well enough alone in the first place would have been the best choice.
|
|/ |
|
|
|
|
|
|
| |
This PR passes all current tests for this feature, and implements the "prefers-color-scheme" media query as an enumerated keyword that is controlled by an integer preference.
Currently, the possible options are 0 to see a website's fallback code and essentially behave like this isn't implemented (our current behavior), 1 to express a preference for a light theme (the default for spec reasons), and 2 to express a preference for a dark theme. Over time, this list may expand to include other preferences like a preference for a sepia theme or something, and this leaves us prepared for that future.
|
|
|
|
| |
Resolves #1719
|
|
|
|
| |
Default false, no intent to ship for web content. Always enabled for Chrome.
|
|
|
|
|
| |
This should be all parts needed to add a brand new enum keyword including
getting the computed style from it...
|
|
|
|
|
|
|
|
|
|
|
| |
ScrollbarStyles contains values of overflow, (over)scroll-behavior, etc.
The only one which is marginally related to scroll _bars_ is overflow, which can
be used to hide scrollbar (by making an element not scrollable) or enforce the
scrollbar to display.
It makes more sense to be called ScrollStyles as it's mainly concerning behavior
of scrolling, not scrollbars. Also, with the addition of scrollbar width
properties, the current name can be confusing.
|
|
|
|
| |
Prepare for scrollbar-width which should trigger the same kind of change.
|
|
|
|
|
| |
This removes android code from base, build, forms, generic, inspector, style,
printing, tools and xul.
|
|
|
|
|
|
|
| |
This avoids overlapping of table styled elements inside flexboxes as used on
some websites.
Resolves #1696
|
|\
| |
| |
| |
| |
| | |
athenian200/UXP:tab-size-length into master
Reviewed-on: https://repo.palemoon.org/MoonchildProductions/UXP/pulls/1674
|
| | |
|
| |
| |
| |
| | |
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.
|
| |
| |
| |
| | |
There were a few typos in the previous patch and this patch also makes tab-size animatable which didn't really require much of a change at all.
|
| |
| |
| |
| | |
Currently -moz-tab-size only accepts <number> values, and both Chrome and Firefox currently support <length> values and have for some time now. So with this you would be able to support sizes in px or em, for instance. This was implemented in Firefox 53 and was trivial to backport.
|
|/
|
|
| |
Closes #1656
|
|\ |
|
| |\
| | |
| | |
| | | |
caret_color
|