summaryrefslogtreecommitdiffstats
path: root/layout/generic/nsTextFrame.cpp
Commit message (Collapse)AuthorAgeLines
* 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.
* 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 1: Nuke most vim config lines in the tree.Moonchild2020-09-23-1/+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 #1355 - Store the dirty rect on the display list builder rather than ↵win7-72020-05-08-1/+0
| | | | | | passing it as a parameter to BuildDisplayList Also fix build bustage for De-unified layout/xul in nsRootBoxFrame.cpp
* Bug 1368547 - Remove nsFrameManagerBase::mPlaceholderMap and instead store ↵Matt A. Tobin2020-04-17-2/+1
| | | | | | the placeholder on a frame property on the out-of-flow Tag #1375
* Revert "Issue #1355 - Better way to create display items for column backgrounds"wolfbeast2020-02-26-0/+1
| | | | This reverts commit 44c47c50388f526c2d134e16d5debebe94a0faf8.
* Issue #1355 - Better way to create display items for column backgroundswin7-72020-02-25-1/+0
| | | | | | | | | | | | | | | | | | | | | | 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.
* Check if we're already at the end of the frame's content.Jonathan Kew2019-12-06-1/+2
|
* Attach FrameProperties to each frame instead of using a shared hashtablewin7-72019-06-26-30/+29
| | | | Dispense the shared hashtable and instead attach the frame property list directly to nsIFrame.
* issue #908 - implement missing parts of CSS maskyami2019-02-02-1/+1
|
* moebius#90: CSS - implement text-justify propertyjanekptacijarabaci2018-04-01-6/+24
|
* Bug 1324042 - Fix trimmedOffsets arithmetic in GetRenderedText(). r=mats, ↵Daniel Holbert2018-03-14-1/+5
| | | | | | | | | | | a=RyanVM MozReview-Commit-ID: H4ngU8Juyln --HG-- extra : rebase_source : f4d6ab58ae70e485dfe72d5290cf6fae2c8397dd extra : intermediate-source : bec50ba1fb12aebde4e4065b2799bc730bc30010 extra : source : fbf54020043bd09c162530907b2a1091a10f4f92
* Add m-esr52 at 52.6.0Matt A. Tobin2018-02-02-0/+10051