summaryrefslogtreecommitdiffstats
path: root/layout/generic
Commit message (Collapse)AuthorAgeLines
* 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
* Bug 1334247 - Remove nsIAnonymousContentCreator::CreateFrameForMatt A. Tobin2020-04-14-8/+0
| | | | Tag #1375
* Bug 1321284 - Crash in nsCSSFrameConstructor::GetInsertionPrevSibling when ↵Matt A. Tobin2020-04-14-1/+3
| | | | | | | | | | | | 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
* Issue #1512 - Improve handling of multiple selections.wolfbeast2020-04-12-1/+1
| | | | | | | | | IsSelectionEditable should check whether the focus node and anchor node aren't null before trying to use them. This also changes the initialization of selections' aOutIndex to the last range in the selection as a fallback in case we don't add a range later (in AddItem) which could also end up with a null selection otherwise if the additional selection nodes are removed.
* [layout] Always move descendants of layout frames if moved.wolfbeast2020-04-10-0/+2
| | | | | If we move the frame then we always need to move any descendant views, not just in case the frame itself has a view.
* Issue #1511 - Bail on orphan situation.wolfbeast2020-04-10-0/+4
| | | | This resolves #1511
* Issue #1485 - Fix incorrect grid cell sizing to min/max space.wolfbeast2020-03-13-29/+29
| | | | | | | | | | | | | | | | There were actually two separate logical errors in this method: The first part is that "origSizes.isSome()" is simply a bogus requirement for applying min/max-sizes here. I'm still keeping the optimization of not needlessly copying the mSizes array (as originally intended) since it's a quite common case. The second bug is that min/max-sizes were only applied under the "if (fr != 0.0f)" block. This is bogus since the calculated 'fr' value depends on 'aAvailableSize' which might change by applying min/max-sizes and thus 'fr' could become non-zero in the second round. To fix, this patch just moves "applyMinMax" block out one level.
* Issue #1480 - Skip abspos, fixed, float and placeholders for outline.wolfbeast2020-03-11-2/+12
|
* Revert "Issue #1355 - Better way to create display items for column backgrounds"wolfbeast2020-02-26-320/+258
| | | | This reverts commit 44c47c50388f526c2d134e16d5debebe94a0faf8.
* Issue #1355 - Better way to create display items for column backgroundswin7-72020-02-25-258/+320
| | | | | | | | | | | | | | | | | | | | | | 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 - Make nsTableCellFrame::GetColIndex/GetRowIndex fasterwin7-72020-02-16-12/+10
| | | | We can devirtualize it, remove some branches.
* Merge branch 'master' of https://github.com/MoonchildProductions/UXP into ↵athenian2002020-01-27-14/+12
|\ | | | | | | form-disabled-issue
| * Bug 1271549 - Remove details and summary preference.Gaming4JC2020-01-26-14/+12
| | | | | | | | Tag UXP Issue #1344
* | Issue #1356 - Remove -moz-user-input disabled to improve event handling.athenian2002020-01-16-0/+18
|/
* Issue #1328 - Part 3: Add fuzz to reftests and fix misc other tests.Chris Peterson2019-12-18-1/+1
|
* Check if we're already at the end of the frame's content.Jonathan Kew2019-12-06-1/+2
|
* Remove unnecessary calls to ReparentFloatsForInlineChild inMats Palmgren2019-11-29-45/+10
| | | | nsInlineFrame.
* Simplify the overflow child frame reparenting inMats Palmgren2019-11-29-7/+2
| | | | nsInlineFrame::DestroyFrom.
* Issue #146 - Part 6: Allow `position: sticky` on table elements.wolfbeast2019-11-03-5/+2
|
* Issue #146 - Part 5: Treat table row groups as containing blocks.wolfbeast2019-11-03-0/+11
| | | | This aligns our behavior with Gecko/Blink.
* Issue #1230 - Part 1: Fix Back-computing percentages for intrinsic sizing in ↵Gaming4JC2019-09-28-233/+93
| | | | | | | | | | | | | | | | | | | | | | Layout CSS-Grid List of relevant patches applied: 1398537 part 2 - [css-multicol] Implement percentages for 'column-gap' (Gecko part). 1434478 part 1 - [css-grid] Stop back-computing percentage grid gaps when the percentage basis is indefinite. Treat them as zero sized instead. 1434478 part 2 - Stop back-computing percentage padding/margin when the percentage basis is indefinite. Treat them as zero sized instead. 1434478 part 3 - Remove IntrinsicISizeOffsetData::hPctPadding/hPctMargin members since they are now unused. 1434478 part 4 - Factor out constants like NS_UNCONSTRAINEDSIZE so they can be used in headers without needing nsIFrame.h (idempotent patch). 1434478 part 5 - Create nsLayoutUtils::ResolveToLength for resolving CSS <length-percentage> (idempotent patch). 1434478 part 6 - Propagate a percentage basis to nsIFrame::IntrinsicISizeOffsets for resolving padding/margin. This is needed only for CSS Grid since in other cases we're only using IntrinsicISizeOffsets in the inline-axis and the percentage basis is always indefinite for *intrinsic sizing*. When calculating the intrinsic size of grid items in the grid container's block axis however, we do have a definite size for the grid area in the inline-axis and it should be used per: https://drafts.csswg.org/css-grid/#algo-overview "2. Next, the track sizing algorithm resolves the sizes of the grid rows, using the grid column sizes calculated in the previous step." (Percentage padding/margin for grid items is always resolved against the grid area's inline-size nowadays.)