summaryrefslogtreecommitdiffstats
path: root/layout/generic
Commit message (Collapse)AuthorAgeLines
* Issue #1705 - Part 5: Implement scrollbar-width:none for all target platforms.Moonchild2021-01-08-12/+27
|
* Issue #1705 - Part 3: Rename ScrollbarStyles to ScrollStyles.Moonchild2021-01-06-27/+27
| | | | | | | | | | | 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.
* Issue #1705 - Part 2: Add a ShowScrollbar enum to be used in ScrollReflowInput.Moonchild2021-01-06-29/+57
| | | | | | | | | | | | | | Overflow properties have two purposes: 1. controlling whether the scrollbar should be shown; 2. controlling whether the content is scrollable. However, with the scrollbar-width property being added, scrollability and presence of a scrollbar are no longer tied together. This patch makes a separation between the value of overflow and the presence of a scrollbar by making it clear that for ScrollReflowInput, we only care about whether scrollbar should be shown. This should make it easier to write the logic involving presence of the scrollbar based on webdev choice.
* Issue #1053 - Part 2a: Remove android from /layout (partial)Moonchild2020-12-26-150/+11
| | | | | This removes android code from base, build, forms, generic, inspector, style, printing, tools and xul.
* Issue #1673 - Part 3: Bring minimum tab advance up to spec.athenian2002020-10-28-11/+30
| | | | This provides a clearer rule for the minimum tab advance that brings us to alignment with the spec and both major browsers.
* Issue #1673 - Part 2: Make tab-size animatable and fix typos.athenian2002020-10-28-3/+3
| | | | 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-29/+45
| | | | 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-2/+1
|\
| * Merge branch 'master' of https://github.com/MoonchildProductions/UXP into ↵athenian2002020-10-18-40/+11
| |\ | | | | | | | | | caret_color
| * | Issue #1668 - Part 2: Visited color and auto support for caret-color property.athenian2002020-10-18-1/+1
| | | | | | | | | | | | 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-2/+1
| | | | | | | | | | | | | | | | | | 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-2/+9
| |/ |/| | | | | | | | | | | | | 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/+3
| | | | | | | | | | | | | | 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 #1665 - Take overflow-wrap into account when calculating min-content ↵Moonchild2020-10-03-0/+10
| | | | | | | | intrinsic size.
* | Issue #1656 - Part 6: Clean up the build filesMoonchild2020-09-23-1/+0
| |
* | Issue #1656 - Part 4: Manual cleanupMoonchild2020-09-23-3/+0
| |
* | Issue #1656 - Part 3: Nuke more vim config lines in the tree.Moonchild2020-09-23-10/+0
| | | | | | | | Another S&R run with some smarter matching.
* | Issue #1656 - Part 2b: Unmangle one more lost little UTF-8 victim.Moonchild2020-09-23-1/+1
| |
* | Issue #1656 - Part 2: Unmangle some unfortunate UTF-8 victims.Moonchild2020-09-23-8/+8
| | | | | | | | The poor fellows got lost in an ASCII-interpretation of the world.
* | Issue #1656 - Part 1: Nuke most vim config lines in the tree.Moonchild2020-09-23-35/+9
|/ | | | | | 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 #1641 - Implement CSS flow-root keywordathenian2002020-09-03-5/+9
| | | | 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.
* Issue #1620 - Remove Development CommentsAndy2020-08-07-4/+0
|
* Issue #1620 - Use Intrinsic Aspect Ratio for ImagesAndy2020-08-04-126/+176
| | | | | | | | | | | | | | | | | 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 - Nits PickedAndy2020-08-02-6/+7
|
* Issue #1619 - Add Vertical Writing TestcaseAndy2020-08-01-20/+0
| | | | | Ensures aspect ratio numerator and denominator aren't swapped in vertical writing modes. https://bugzilla.mozilla.org/show_bug.cgi?id=1548768
* Issue #1619 - Convert Intrinsic Ratio to FloatAndy2020-07-31-103/+182
| | | | | | | | | 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
* Merge pull request #1576 from win7-7/1379306-prMoonchild2020-06-04-2/+2
|\ | | | | Fix the wrong position when we calculate the position for position:absolute child
| * issue #1575 - Fix the wrong position when we calculate the position for ↵win7-72020-06-02-2/+2
| | | | | | | | | | | | position:absolute child and add reftests Use |GetUsedBorder| instead of |GetComputedBorder| when we calculate the position for position:absolute child.
* | Issue #1525 - Kill marquee elementMoonchild2020-06-01-332/+0
|/ | | | | | * Remove marquee code * Regenerate HTML Elements/parser code for Removal of Marquee. Co-authored-by: Gaming4JC <g4jc@hyperbola.info>
* Revert "Merge pull request #1357 from athenian200/form-disabled-issue"athenian2002020-05-20-18/+0
| | | | | 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-17/+9
| | | | | This prevents the Alt text from briefly being shown before being replaced with the image.
* Issue #1543 - Align <img> with no src to the updated spec.Moonchild2020-05-11-55/+59
|
* Issue #1355 - Fix the nit, remove nsPoint offset in nsFrame.cpp and change ↵win7-72020-05-10-2/+1
| | | | PresShellState member order
* Issue #1355 - Better way to create display items for column backgroundswin7-72020-05-08-4/+40
| | | | | | | | | | | | | | | | | | | | | | Part 1: Remove current table item, as it's never set. Part 2: Get rid of generic table painting code, and handle each class separately. Part 4: Hoist outline skipping into col(group) frame code. Part 5: Skip box-shadow for table column and column groups. Part 6: Store column and column group backgrounds separately, and then append them before the rest of the table contents. Part 7: Pass rects in display list coordinates to AppendBackgroundItemsToTop. Part 8: Create column and column group background display items as part of the cell's BuildDisplayList. Part 9: Used cached values instead of calling nsDisplayListBuilder::ToReferenceFrame when possible, since it can be expensive when the requested frame isn't the builder's current frame. Part 10: Make sure we build display items for table parts where only the normal position is visible, since we may need to create background items for ancestors at that position. Part 11: Create an AutoBuildingDisplayList when we create background items for table columns and column groups, so that we initialize the invalidation state correctly.
* Issue #1355 - Avoid unnecessary work in ↵win7-72020-05-08-47/+53
| | | | | | | | | | nsIFrame::BuildDisplayListForStackingContext() and nsIFrame::BuildDisplayListForChild() and Cleanup DescendIntoChild Bug 1441796 - Part 1: Optimize the (pseudo)-stacking context conditions Bug 1441796 - Part 3: Reuse the results in nsIFrame::BuildDisplayListForStackingContext() for ChildrenHavePerspective(), IsTransformed(), and Combines3DTransformWithAncestors() Bug 1512244 - Part 1: Cleanup DescendIntoChild
* Issue #1355 - Preemptively fix build bustage for 1409114win7-72020-05-08-8/+8
|
* Issue #1355 - Store the dirty rect on the display list builder rather than ↵win7-72020-05-08-192/+146
| | | | | | passing it as a parameter to BuildDisplayList Also fix build bustage for De-unified layout/xul in nsRootBoxFrame.cpp
* Issue #80 - Resolve issues with compiling on insane gcc configurations with ↵Moonchild2020-05-01-1/+1
| | | | | | no optimizations in layout/ (and fix a typo for cs fs)
* Issue #80 - De-unify layout/PITA... I mean layout/genericMoonchild2020-04-29-8/+21
|
* Bug 1422197 - Add fast path to get DocGroup in binding code for [CEReactions]Matt A. Tobin2020-04-17-0/+16
| | | | Tag #1375
* Bug 1381134 - Ensure we're using the correct frame for the :after/:before ↵Matt A. Tobin2020-04-17-0/+92
| | | | | | references Tag #1375
* Bug 1377978 - Make nsRange use uint32_t to offsetMatt A. Tobin2020-04-17-7/+13
| | | | Tag #1375
* Bug 1377648 - Fix HTMLSummaryElement::IsSummary() on removing the elementMatt A. Tobin2020-04-17-0/+15
| | | | | | | * Use inFlowFrame to check the target frame is summary and its parent is details * Check summary frame instead of summary element on removing the summary Tag #1375
* Bug 1368547 - Remove nsFrameManagerBase::mPlaceholderMap and instead store ↵Matt A. Tobin2020-04-17-45/+37
| | | | | | the placeholder on a frame property on the out-of-flow Tag #1375
* Bug 1367683 - Optimize initializing nsRangeMatt A. Tobin2020-04-17-54/+31
| | | | Tag #1375
* Bug 1355351 - Make pseudo-elements return the correct style via getComputedStyleMatt A. Tobin2020-04-17-13/+6
| | | | | | | | | * 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 1343937 - Fix a crash in nsWrapperCache.hMatt A. Tobin2020-04-16-2/+22
| | | | | | | * Implement and use GetInFlowParent * Exempt scrollbar NAC from the new NAC semantics Tag #1375
* Bug 1340885 - Null check frame's content when searching for NAC ancestors in ↵Matt A. Tobin2020-04-16-1/+2
| | | | | | GetCorrectedParent Tag #1375
* Bug 1331322 - Allow tagging of pseudo-implementing native anonymous content ↵Matt A. Tobin2020-04-16-5/+30
| | | | | | | | | | | 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
* Bug 1334358 - Remove nsCSSFrameConstructor::CreateAnonymousFramesMatt A. Tobin2020-04-14-1/+2
| | | | Tag #1375
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-29 08:33:23 +0000