summaryrefslogtreecommitdiffstats
path: root/layout/style
Commit message (Collapse)AuthorAgeLines
* Issue #1673 - Part 5: Fix brace style and missed -moz-tab-size reference.athenian2002020-10-29-255/+212
|
* Issue #1673 - Part 4: Unprefix -moz-tab-size.athenian2002020-10-28-7/+18
| | | | 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.
* Issue #1673 - Part 2: Make tab-size animatable and fix typos.athenian2002020-10-28-2/+4
| | | | 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.
* Issue #1673 - Part 1: Allow tab-size to accept <length>.athenian2002020-10-28-33/+79
| | | | 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.
* Merge branch 'master' of https://github.com/MoonchildProductions/UXPMoonchild2020-10-20-10/+113
|\
| * Merge branch 'master' of https://github.com/MoonchildProductions/UXP into ↵athenian2002020-10-18-173/+190
| |\ | | | | | | | | | caret_color
| * | Issue #1668 - Part 2: Visited color and auto support for caret-color property.athenian2002020-10-18-7/+25
| | | | | | | | | | | | Mozilla's original implementation of this failed a couple of tests, but this seems to solve all the problems. Basically, the caret-color wasn't able to be set differently based on whether a link was visited, and the auto value implementation was incomplete. The only test we fail now is the one where you have grey text on a grey background and the caret is supposed to be visible, but I think that may have been removed from the spec. Even if it wasn't, no other browser supports it anyway.
| * | Issue #1668 - Part 1: Implement support for caret-color property.athenian2002020-10-18-9/+94
| | | | | | | | | | | | | | | | | | 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
* | | Issue #1671 - Unprefix ::-moz-selectionMoonchild2020-10-20-0/+3
| |/ |/| | | | | | | | | | | | | 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.
* | Issue #1666 - Implement overflow-wrap: anywhereMoonchild2020-10-03-2/+8
| | | | | | | | | | | | | | This aligns with the current spec regarding overflow-wrap: break-word and overflow-wrap: anywhere in if it affects intrinsic sized due to considering soft-wrap opportunities or not. See CSS Text Module Level 3, Editor’s Draft, 1 October 2020, Section 5.5
* | Issue #1647 - Followup: Remove excessive VARIANT_OPACITY statements.athenian2002020-09-30-6/+6
| | | | | | | | | | | | | | | | I got very anxious about making sure I included VARIANT_OPACITY in all the places VARIANT_NUMBER was included to make sure it couldn't possibly break unexpectedly, and that led to me accidentally breaking a mechanism that prevented percentages from serializing as numbers in other parts of the code. It was a total accident, and these additions were unnecessary. Basically, the situation is that there was one part of the code where it determines what's allowed for the flex statement (and possibly other statements) by checking whether it got stored as a "number", and basically only disallows percentages if it attempted to store/serialize them as percentages. However, it only got to that part of the code because I accidentally allowed VARIANT_OPACITY as a valid way for certain tokens to parse where it wasn't necessary. If it tries to parse it that way under very specific circumstances... percentages will be marked valid and fed through the system as numbers rather than being rejected and not serialized at all, because the check to disallow percentages there relied on them being stored as percentages. It's a really weird thing to have a problem with in a lot of ways, because if percentages aren't allowed in a field, you would think people wouldn't try to use them there, much less depend on the broken behavior that results from them not parsing as a related value.
* | Issue #1656 - Part 8: Devtools and misc.Moonchild2020-09-24-2/+0
| |
* | Issue #1656 - Part 6: Clean up the build filesMoonchild2020-09-23-2/+0
| |
* | Issue #1656 - Part 4: Manual cleanupMoonchild2020-09-23-15/+0
| |
* | Issue #1656 - Part 3: Nuke more vim config lines in the tree.Moonchild2020-09-23-8/+0
| | | | | | | | Another S&R run with some smarter matching.
* | Issue #1656 - Part 1: Nuke most vim config lines in the tree.Moonchild2020-09-23-51/+0
| | | | | | | | | | | | Since these are just interpreted comments, there's 0 impact on actual code. This removes all lines that match /* vim: set(.*)tw=80: */ with S&R -- there are a few others scattered around which will be removed manually in a second part.
* | Issue #1655: Update MediaQueryList to the current draft spec.Moonchild2020-09-23-87/+176
|/ | | | | | | This make MediaQueryList inherit from EventTarget and adds MediaQueryListEvent as an interface as well as the onchange() method. This should not affect compatibility with other code; the event object is a MediaQueryListEvent instance, which is recognized as a MediaListQuery instance.
* Merge pull request #1654 from athenian200/opacity_percentageMoonchild2020-09-18-23/+36
|\ | | | | Implement percentage for CSS opacity keywords
| * Issue #1647 - Part 2: Implement VARIANT_OPACITY to correctly serialize.athenian2002020-09-17-33/+31
| | | | | | | | Even though percentages are already treated as floats internally by the style system for computation purposes, you have to go out of your way to stop them from being read back out as percentages. What I do here amounts to storing the percentage token in the "wrong" container, the one normally used for floats. This allows a value that was read in as a percentage to be read back out as something else, which is normally prevented by the design of the style system.
| * Issue #1647 - Part 1: Implement percentage for CSS opacity keywordsathenian2002020-09-16-14/+29
| | | | | | | | | | This preliminary step allows percentages to be computed and display correctly, but unfortunately it fails a test after changing VARIANT_HN to VARIANT_HPN because that allows values to be serialized as percentages. However, not doing this means percentages are rejected as valid values for the user to input. The way the style system is setup makes it hard to change this for opacity without changing it for everything else, especially since some code-saving speed hacks in Bug 636029 and Bug 441367 that make a lot of assumptions about this stuff very rigid.
* | Merge pull request #1651 from athenian200/link_element_disabledMoonchild2020-09-13-5/+7
|\| | | | | Clean up local variables from <link> disabled issue.
| * Issue #1629 - Part 5: Remove pointless local variables.athenian2002020-09-09-8/+7
| | | | | | | | Since the local variable is always initialized to false, we don't actually need to declare it and can just pass "false" directly as a parameter to the PrepareSheet function's bool. I was worried about code readability at first, but some well-placed comments took care of that.
| * Issue #1629 - Part 4: Ensure isExplicitlyEnabled is false upon sheet creation.athenian2002020-09-06-2/+5
| | | | | | | | This clarifies the assumptions the code is making and the order in which the variables pass through the loading process. The new variable is set after the sheet is created and prepared, and is assumed to be false in the beginning.
* | Issue #1641 - Implement CSS flow-root keywordathenian2002020-09-03-2/+15
| | | | | | | | This is just a clean port of 1322191 and follow-up 1325970. It really seems to add create a new way to access existing code relating to block formatting and floating elements rather than implementing new functionality, and it is mercifully straightforwards.
* | Merge pull request #1632 from athenian200/link_element_disabledMoonchild2020-08-18-13/+28
|\| | | | | Respond to disabled attribute set on <link> elements from HTML
| * Issue #1629 - Part 2: Implement the Explicitly Enabled flag.athenian2002020-08-13-13/+28
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This part of the bug was significantly complicated by the following major refactors: https://bugzilla.mozilla.org/show_bug.cgi?id=1456435 https://bugzilla.mozilla.org/show_bug.cgi?id=1459498 As best as I can tell, we just need to implement the explicitly enabled flag on every instance of GetStyleSheetInfo, make sure aIsExplicitlyEnabled is false in every situation except the one where the disabled content attribute is removed from a link element, and enable alternate stylesheets if this flag is set on them. So we take the explicitly enabled flag as an input to PrepareSheet, and also add it to LoadStyleLink and LoadInlineStyle. I also decided not to defer loading of alternate stylesheets that have been explicitly enabled.
* | Issue #1620 - Intrinsic Aspect Ratio: Debug Follow up.Gaming4JC2020-08-16-0/+2
| | | | | | | | | | | | | | Newly introduced aspect-ratio property did not have CSS_PROP_LIST_EXCLUDE_INTERNAL defines, resulting in the following assertion: \!nsCSSProps::PropHasFlags(p, (1<<28)) (properties defined outside of #ifndef CSS_PROP_LIST_EXCLUDE_INTERNAL sections must not have the CSS_PROPERTY_INTERNAL flag), at ...layout/style/nsCSSProps.cpp:289 This patch resolves the assertion by adding #ifndef around the aspect-ratio property.
* | [CSS] Alias -webkit-appearance for compatibility reasonsMoonchild2020-08-10-0/+5
| | | | | | | | | | | | | | | | | | | | Since this is supported as an alias by Firefox and Edge for the same reasons and we have websites using this to (attempt to) override the system-provided styling with their own, leaving out the only supported keyword we'd otherwise have (with -moz- prefix) but still stating -webkit-. TODO: unprefix this completely and make the vendor prefixes aliases.
* | Issue #1620 - Use Intrinsic Aspect Ratio for ImagesAndy2020-08-04-0/+26
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | https://bugzilla.mozilla.org/show_bug.cgi?id=1547231 https://bugzilla.mozilla.org/show_bug.cgi?id=1559094 https://bugzilla.mozilla.org/show_bug.cgi?id=1633434 https://bugzilla.mozilla.org/show_bug.cgi?id=1565690 https://bugzilla.mozilla.org/show_bug.cgi?id=1602047 Make use of Aspect Ratios in Image frames before Images are loaded. - Check for width and height HTML properties and create a ratio with them. - Overwrite HTML size values with actual image dimensions on load. - Collapse any frames with srcless images. Comments: dom/html/nsGenericHTMLElement.cpp:1483 layout/generic/nsImageFrame.cpp:289
* | Issue #1619 - Convert Intrinsic Ratio to FloatAndy2020-07-31-2/+2
|/ | | | | | | | | https://bugzilla.mozilla.org/show_bug.cgi?id=1547792 Aspect Ratio handling simplified by using floating point integers: - Multiplication of value (or inverse value) to a known side for Scaling - No unequal equal values such as "4/3" vs "8/6" vs "20/15" - Truly "Empty" aspect ratios, even if one dimension is not 0
* Issue #1525 - Kill marquee elementMoonchild2020-06-01-789/+0
| | | | | | * Remove marquee code * Regenerate HTML Elements/parser code for Removal of Marquee. Co-authored-by: Gaming4JC <g4jc@hyperbola.info>
* Issue #1564 - Split off nsIdentifierMapEntry in its own headerwolfbeast2020-05-25-0/+1
| | | | + Fix dependency fallout from removing nsDocument.h from ShadowRoot.h
* Revert "Merge pull request #1357 from athenian200/form-disabled-issue"athenian2002020-05-20-1/+6
| | | | | This reverts commit ed88b99849156004c04e4a0c87ea9b2360ef19b6, reversing changes made to c4b0715baaffc541670fd1158557aa7e61e521d3.
* Issue #1543 - Follow-up: avoid displaying the Alt text if an image is loading.Moonchild2020-05-12-1/+0
| | | | | This prevents the Alt text from briefly being shown before being replaced with the image.
* Issue #80 - Resolve issues with compiling on insane gcc configurations with ↵Moonchild2020-05-01-0/+3
| | | | | | no optimizations in layout/ (and fix a typo for cs fs)
* Issue #80 - De-unify layout/styleMoonchild2020-04-30-15/+39
|
* Bug 1425769 - Base class for ShadowRoot and Document to manage style stateMatt A. Tobin2020-04-17-4/+4
| | | | Tag #1375
* Issue #80 - De-unify dom/baseMatt A. Tobin2020-04-17-0/+1
| | | | Tag #1375
* Bug 1417829 - Remove unresolved pseudoclassMatt A. Tobin2020-04-17-3/+0
| | | | Tag #1375
* Bug 1422197 - Add fast path to get DocGroup in binding code for [CEReactions]Matt A. Tobin2020-04-17-0/+66
| | | | Tag #1375
* Bug 1409975 - Implement node distribution for shadow tree slotsMatt A. Tobin2020-04-17-0/+6
| | | | | | | | | | * Implementation for assignedNodes * Include slots in the flat tree * Fix event get-the-parent algorithm for a node * Update and add reftests for Shadow DOM v1 * Update web platform tests expectations Tag #1375
* Bug 1416999 - Remove document.registerElementMatt A. Tobin2020-04-17-14/+14
| | | | Tag #1375
* Bug 1373798 - Move HTML dir attribute state into event state flagsMatt A. Tobin2020-04-17-7/+25
| | | | | | | | | | * Stop calling SetHasDirAuto/ClearHasDirAuto in input element code * Introduce event state flags that track the state of an element's dir attribute * Rewrite our existing checks for the state of the dir attr on top of the new event state flags * Add pseudo-classes for matching on the dir attribute states * Use the new dir attribute pseudoclasses in html.css Tag #1375
* Bug 1332353 - Make it clearer when a stylesheet is really owned by its mDocumentMatt A. Tobin2020-04-17-24/+69
| | | | Tag #1375
* Bug 1355351 - Make pseudo-elements return the correct style via getComputedStyleMatt A. Tobin2020-04-17-4/+43
| | | | | | | | | * Add a node property to access the ::before and ::after pseudo-elements * Look for the frame for ::before and ::after pseudos * Clean up pseudo-element props * Simplify nsLayoutUtils callers, and make child iterators notice display: contents pseudos Tag #1375
* Bug 1330843 - Allow JS to create NAC pseudo-elementsMatt A. Tobin2020-04-17-2/+14
| | | | Tag #1375
* Bug 1346623 - Allow anonymous content created with ↵Matt A. Tobin2020-04-16-0/+61
| | | | | | | | | nsIDocument::InsertAnonymousContent can change from non-native to native AC * Prevent canvas custom content from becoming NAC when reframing the root element * Add an API to get computed style values through an AnonymousContent object Tag #1375
* Bug 1331322 - Allow tagging of pseudo-implementing native anonymous content ↵Matt A. Tobin2020-04-16-0/+2
| | | | | | | | | | | with the pseudo type at creation time * Stop using a node bit for HasExplicitBaseURI * Move MAY_HAVE_CLASS to mBoolFlags * Add a flag to indicate that a node is native anonymous content * Allow tagging of pseudo-implementing native anonymous content with the pseudo type at creation time, and eliminate explicit style contexts in nsIAnonymousContentCreator::ContentInfo Tag #1375
* Issue #1375 - Fix unified sourcesMatt A. Tobin2020-04-14-4/+7
|
* Bug 1321284 - Crash in nsCSSFrameConstructor::GetInsertionPrevSibling when ↵Matt A. Tobin2020-04-14-0/+80
| | | | | | | | | | | | trying to reframe native anonymous content * Make StyleChildrenIterator skip NAC generated by root element primary frame ancestors. * Add nsINode::GetFlattenedTreeParentNodeForStyle. * Add iterator class to find all restyle roots. NOTE: Parts 1, 2, and "4.2" Tag #1375
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-10 18:05:51 +0000