wuggy/Dactyloidae
wuggy/Dactyloidae
1
0
Fork 0
mirror of https://repo.dactyloidae.xyz/Dactyloidae/UXP.git synced 2026-09-05 15:28:39 +09:00
Code Issues Projects Releases Packages Wiki Activity
5,172 commits 7 branches 15 tags 557 MiB
Commit graph

434 commits

Author SHA1 Message Date
FranklinDM
ef36c56593 Issue #2137 - Part 4: Fix namespace regression 2023-03-12 07:09:56 +08:00
FranklinDM
b257a71cce Issue #2137 - Part 3: Don't always use the internal pseudo-class for handling negations 2023-03-12 07:09:41 +08:00
FranklinDM
3bb3c193d0 Issue #2137 - Part 2: Implement SelectorParsingFlags and use it to pass info around 2023-03-12 07:09:22 +08:00
FranklinDM
82fa9fb80b Issue #2137 - Part 1: Modify :not() selector to accept a complex selector list 2023-03-12 07:09:00 +08:00
Moonchild
2249fbdf49 Issue #2135 - Follow-up: Check for aElement not being null 
This was introduced to Make <link rel="stylesheet"> work in shadow trees.
eElement can, however, be `null` here and if so, it would crash.
 2023-03-12 07:07:25 +08:00
Martok
2b903a20b3 Issue #2143 - Implement CSS env() Environment Variables 2023-03-07 11:17:39 +08:00
FranklinDM
21d468ee65 Issue #2136 - Part 1: Implement CSS inset property 2023-03-06 16:27:53 +08:00
FranklinDM
7924a2f60d Issue #2135 - Bug 1329877: Optimize AncestorFilter usage in lazy frame construction 2023-03-06 16:20:24 +08:00
FranklinDM
588c2154a5 Issue #2135 - Bug 1410578: Make <link rel="stylesheet"> work in shadow trees 2023-03-06 16:17:01 +08:00
FranklinDM
45c179d01b Issue #2135 - Bug 1453789: Remove Element.createShadowRoot 2023-03-06 16:16:40 +08:00
FranklinDM
010db07bf3 Issue #2135 - Bug 1066965: Make contentEditable and spellchecking to work in Shadow DOM 2023-03-06 16:16:21 +08:00
FranklinDM
b40c87a59a Issue #1375 - Follow-up: Get the insertion point right when reconstructing direct children of a shadow root 
This should've been changed alongside bug 1404789 when it landed.
 2023-02-28 10:45:05 +08:00
FranklinDM
6a26ce3455 Issue #1375 - Follow-up: Remove shadow tree hacks in the frame constructor 
This should've been removed alongside bug 1404789 when it landed.
 2023-02-28 10:44:45 +08:00
FranklinDM
edc45f6849 Issue #1593 - Follow-up: Fix :host selector matching 
Previously, we would match `:host` if:
(a) we don't have any arguments and our parent is the shadow root, or;
(b) if any of the arguments match, then reject if we don't have a containing shadow

Revised, we would match `:host` if:
(Preconditions) The element must have a shadow root, the selector must not have any feature selectors, and it is not blocked from matching `:host` (e.g. .matches outside of the shadow root context)
(a) The selector does not have any arguments, or;
(b) It matches any of its arguments in the functional part of the pseudo-class

With this, we now pass these tests that were previously failing:
http://wpt.live/css/css-scoping/css-scoping-shadow-host-rule.html
http://wpt.live/css/css-scoping/host-descendant-002.html
http://wpt.live/css/css-scoping/host-multiple-001.html
Improved (1 less red box):
http://wpt.live/css/css-scoping/css-scoping-shadow-host-namespace.html
 2023-02-27 11:03:50 +08:00
FranklinDM
ebe27baa23 Issue #1382 - Part 2: Add crash test 
Based on https://bugzilla.mozilla.org/show_bug.cgi?id=842114
 2023-02-27 11:03:31 +08:00
FranklinDM
691afc8c8b Issue #1382 - Part 1: Remove assertion that GetPreEffectsVisualOverflowRect is called only by frames whose parent is an anonymous block 
This is always hit if an SVG effect is applied on other frame types.

Based on https://bugzilla.mozilla.org/show_bug.cgi?id=1340257
 2023-02-27 11:03:05 +08:00
FranklinDM
439c671b26 Issue #2078 - Follow-up: Propagate combinator restriction to :is()/:where() 
Based on spec discussion: https://github.com/w3c/csswg-drafts/issues/5093
 2023-02-23 21:15:40 +08:00
FranklinDM
83484a34f5 Issue #2078 - Follow-up: aPreventComplexSelectors should be passed 2023-02-23 21:15:12 +08:00
FranklinDM
53f5905381 Issue #2078 - Follow-up: Move isForgiving check to ParsePseudoClassWithSelectorListArg 2023-02-23 21:14:58 +08:00
FranklinDM
03a3385702 No issue - Move Has* function definition out of the header file for consistency 2023-02-23 21:14:41 +08:00
FranklinDM
9037d5662d Issue #1593 - Follow-up: Accept only a single selector in the argument of :host/:host-context 
Current spec says these two pseudo-classes accept only a single compound selector:
:host( <compound-selector> )
:host-context( <compound-selector> )
 2023-02-22 07:07:39 +08:00
FranklinDM
0391e8ab09 Issue #1593 - Follow-up: Copy mIsRelevantLink value over rather than calling IsLink 
Calling IsLink ignores whatever state we have for aTreeMatchContext and will trigger an assertion if aTreeMatchContext.mForStyling is false. This also adds a comment about what that line effectively does.
 2023-02-22 07:07:21 +08:00
FranklinDM
9bebb3a61a Issue #1593 - Follow-up: :host() should not automatically match if we have a non-empty selector list 2023-02-22 07:07:01 +08:00
FranklinDM
ba7e29a052 Issue #1823 - Ensure :host() and :host-context() are given proper weights 2023-02-22 07:06:43 +08:00
FranklinDM
6d77f755da Issue #2078 - Part 6: Replace empty list head with the next non-empty list for forgiving selector lists 
What happens here if aListHead is an empty selector list:
(1) next selector group is parsed and continues to the next iteration if it's empty or invalid
(2) if we're a forgiving selector list and aListHead is empty, replace it with the selector group that we've just parsed
(3) step 1 ignores invalid/empty, so we assert that step 2 should never have an empty selector list
 2023-02-22 07:06:24 +08:00
FranklinDM
4ece7873e0 Issue #2078 - Part 5: Ensure :is() and :where() are given proper weights 2023-02-22 07:06:05 +08:00
FranklinDM
1c1473166f Issue #2078 - Part 4: Unify selector list matching 
This should allow pseudo-classes that accept selector lists to properly handle complex selectors. `:visited` is also matched inside selector lists.
A previous iteration of this commit had incorrect matching behavior when called from `RestrictedSelectorListMatches`.
 2023-02-22 07:05:44 +08:00
FranklinDM
14e8922dca Issue #2078 - Part 3: Rename nsCSSRuleProcessor::SelectorListMatches to RestrictedSelectorListMatches 
This is in preparation for merging the logic of RestrictedSelectorListMatches and AnySelectorInArgListMatches.
 2023-02-22 07:05:25 +08:00
FranklinDM
0648ec64bb Issue #2078 - Part 2: Rename nsPseudoClassList->u.mSelectors to mSelectorList 
This makes it clear that we're accessing a selector list (nsCSSSelectorList), which is different from the selectors (nsCSSSelector) contained inside a selector list. Previously, both were confusingly referred to as mSelectors.
 2023-02-22 07:05:08 +08:00
FranklinDM
453b715ef6 Issue #2078 - Part 1: Update CSS rule processor to handle :is() and :where() CSS pseudo-classes 
This modifies selector list parsing to accommodate being "forgiving". Aliases for the :is selector's former names were also included. Note that the older and prefixed variant `-moz-any` remains unforgiving.
 2023-02-22 07:04:49 +08:00
FranklinDM
6d3500bb48 Issue #2111 - Implement CSSStyleRule.selectorText setter 
Unlike the original patch, this copies Chrome behavior: ignores invalid values of selectorText without any console log.

Partially based on https://bugzilla.mozilla.org/show_bug.cgi?id=37468
 2023-02-21 08:20:21 +08:00
Job Bautista
cc6b0f11e7 Issue #2107 - Clean up caret when destroying editor. 
Editor changes caret visibility during drag and drop. But when destroying
editor, we don't restore caret state. So we should restore it when destroying
editor.

Co-authored-by: Makoto Kato <m_kato@ga2.so-net.ne.jp>
 2023-02-20 11:11:02 +08:00
FranklinDM
4c9665a4ae Issue #2104 - Part 2: Indicate if a label was cropped via the "_is_cropped" attribute 2023-02-08 16:57:11 +08:00
FranklinDM
60c344a56b Issue #2104 - Part 1: Implement "clip" attribute value for XUL string cropping 
This implements the "clip" attribute value for the "crop" attribute found in XUL label elements. It functions similarly to having the text-overflow property set to an empty string or "". This shouldn't break previously established behavior as it only adds a new value to be checked.

The behavior of the "none" attribute value in the documentation (https://udn.realityripple.com/docs/Archive/Mozilla/XUL/Attribute/crop) is incorrect. The "none" attribute value literally means "don't crop anything" if you'd check the code and is also equivalent to not setting the "crop" attribute at all. This has always been the case since Firefox 2 (earliest version I checked) and apparently, this section of the documentation was copied verbatim from XULPlanet without even checking if it's correct.
 2023-02-08 16:56:51 +08:00
FranklinDM
56e636d8ec Issue #2084 - Part 2: Simplify logic in CSSParserImpl::LookupKeywordPrefixAware 
Based on https://bugzilla.mozilla.org/show_bug.cgi?id=1259348
 2023-01-10 07:41:39 +08:00
FranklinDM
db3ce13f28 Issue #2084 - Part 1: Remove CSSUnprefixingService.js and associated code 
It's effectively dead code since it's been supplanted by built-in webkit-prefixed-CSS support (landed before fork point in Firefox 49).

Based on https://bugzilla.mozilla.org/show_bug.cgi?id=1259348
 2023-01-10 07:37:30 +08:00
Moonchild
e38f362d44 Issue #2075 - Part 5: Allow logical aliases in the property database. 2023-01-06 20:36:35 +08:00
Moonchild
1b22ef40f9 Issue #2075 - Part 4: Update tests 
* Update reftests to use inset-*
* Update property database
* Update logical properties test
 2023-01-06 20:36:22 +08:00
Moonchild
07af4123d1 Issue #2075 - Part 2: Update devtools for inset-* 2023-01-06 20:35:53 +08:00
Moonchild
0c37c0db8f Issue #2075 - Part 1: Rename offset-* logical properties to inset-* 
This adds aliases behind a pref with the old offset-* names
 2023-01-06 20:35:40 +08:00
Job Bautista
ca3361fb57 Issue #2068 - Only wrap the last line of inline elements when positively padding to the right. 
This fixes the 21 year old Mozilla bug 122795.

Co-authored-by: Jonathan Kew <jfkthame@gmail.com>
 2022-12-30 09:21:14 +08:00
Job Bautista
09cbcd3413 Issue #2063 - Ensure a floated ::first-letter inherits from ::first-line. 
This fixes the 24 year old Mozilla bug 13610.

Co-authored-by: Ryo Onodera <ryoqun@gmail.com>
 2022-12-30 09:09:13 +08:00
Martok
3f073056de Issue #2030 - Pref-gate default button event dispatch logic 2022-12-02 23:56:21 +08:00
Martok
4354c7a1bc Issue #2030 - Allow child nodes of button to participate in mouse hit tests 
This is needed for web compatibility, even if standards compliance is debatable.
 2022-12-02 23:55:57 +08:00
Martok
4d310562d9 Issue #2030 - (chore) refactor event dispatch functions 
Based on selected bits of M-C 1461708:
- EventStateManager::CheckForAndDispatchClick() to early-return style
- split EventStateManager::CheckForAndDispatchClick() into:
  EventCausesClickEvents, PostHandleMouseUp, DispatchClickEvents
- Move implementation of UIEvent::GetRangeParent() and UIEvent::RangeOffset() to nsLayoutUtils
 2022-12-02 23:55:37 +08:00
Moonchild
1868e88741 Fix some debug assertions. 
refactored code porting in assertions causing debug build failures.
 2022-10-06 10:26:38 +08:00
roytam1
52a48df032 Revert "Issue #1986 - Use logical coordinates in flex containers." 
This reverts commit 7527371d78.
 2022-09-29 15:18:18 +08:00
roytam1
c522a01d6c Revert "Issue #1986 - Part 2: Add IsItemInlineAxisMainAxis() and rework some nsFrame code." 
This reverts commit c3e18955ad.
 2022-09-29 15:18:10 +08:00
roytam1
e46011bcc3 Revert "Issue #1986 - Add in reftests for new behavior." 
This reverts commit cf5dfc5e7d.
 2022-09-29 15:18:00 +08:00
Moonchild
fa8bc1e81c Issue #1992 - Part 1: Un-prefix -moz-{min|max}-content keywords. 2022-09-23 11:03:34 +08:00