summaryrefslogtreecommitdiffstats
path: root/layout
Commit message (Collapse)AuthorAgeLines
* Fix comments for Framepropertieswin7-72019-07-12-2/+2
| | | | | | | | | | https://bugzilla.mozilla.org/show_bug.cgi?id=1373884 Fixes comments for Frameproperties. These comments went unnoticed earlier. No code changes.
* Iterate the frame property list once to collect which child list properties ↵win7-72019-07-08-36/+80
| | | | | | we have Look into optimizing out the hashtable lookups from nsContainerFrame
* Avoid multiple hashtable lookups in DisplayItemData destructorwin7-72019-07-07-2/+7
| | | | | | | | | | | UXP has: MOZ_RELEASE_ASSERT(sAliveDisplayItemDatas && sAliveDisplayItemDatas >Contains(this)); sAliveDisplayItemDatas->RemoveEntry(this); and this gets hit during frame destruction. Combine these checks.
* Attach FrameProperties to each frame instead of using a shared hashtablewin7-72019-06-26-944/+726
| | | | Dispense the shared hashtable and instead attach the frame property list directly to nsIFrame.
* Revert "Improve origin-clean algorithm"wolfbeast2019-06-04-5/+3
| | | | This reverts commit e69b3f567c4b8957cc09ba4359e84939f77781c5.
* Improve origin-clean algorithmwolfbeast2019-05-27-3/+5
|
* Lots of time spent maintaining nsDisplayLayerEventRegions (#1116)win7-72019-05-24-0/+4
| | | | | | | | * Simplify the dispatch-to-content region Simplify the dispatch-to-content region in nsDisplayLayerEventRegions::AddFrame() and AddInactiveScrollPort() if it starts to get large. * tabs to spaces
* Issue #1101 - Support gzip-compressed SVGs in OpenType+SVG fontsGaming4JC2019-05-23-0/+31
|
* Merge pull request #1071 from win7-7/nsDisplayListBuilderMoonchild2019-05-03-2/+2
|\ | | | | nsFrameList::GetLength() calls in nsDisplayListBuilder::MarkFramesForDisplayList() are slow
| * patch to Bug 1377329win7-72019-05-02-2/+2
| |
* | unnecessary space at the end removedwin7-72019-05-02-1/+0
| |
* | patch to Bug 1363423win7-72019-05-02-0/+5
|/
* Capture delayed events and cancel as necessary.wolfbeast2019-04-26-0/+16
| | | | Tag #1052
* Handle URL token in a closer way to the CSS3 specJustOff2019-04-20-14/+33
|
* Issue #991 Part 5: DOM and layoutAscrod2019-04-13-79/+15
|
* Add nullcheck in nsSVGUtils::PaintFrameWithEffectswolfbeast2019-04-06-3/+6
| | | | | | Some SVGs define a mask but an invalid mask frame. Check to make sure we have a `maskFrame` that isn't null before trying to use it. This resolves #1034
* Revert "add a nullptr check in nsSVGUtils::PaintFrameWithEffects"wolfbeast2019-04-06-1/+1
| | | | This reverts commit 00baf283622b47ad7926c6e62364854d3dfbc00a.
* add a nullptr check in nsSVGUtils::PaintFrameWithEffectsyami2019-04-03-1/+1
|
* Bug 1360343 - ensure maskSurface is not null before dereference, since it ↵cku2019-04-03-1/+2
| | | | | | | | | can be null because of OOM or gfx device reset. r=dvander MozReview-Commit-ID: HX2qsWLZpMg --HG-- extra : rebase_source : 046befc11151461a682842c31e2ce39247a5e1d8
* Remove 18 yo OS/2 and AIX bustage workaround.wolfbeast2019-03-31-19/+73
| | | | Tag #186
* Issue #187: Remove solaris conditional code.wolfbeast2019-03-30-3/+0
|
* Grab caching capturing content with local variable.wolfbeast2019-03-23-5/+5
|
* The result of adding any percentage factor to a size that is zero should ↵JustOff2019-03-21-4/+5
| | | | also be zero
* Handle the special case of a flex frame being the absolute containing block ↵JustOff2019-03-14-6/+148
| | | | correctly from the CSS align code
* Remove various hard-coded Accept: headerswolfbeast2019-03-07-4/+0
| | | | | | | Since we're now handling this in the network back-end, there's no need for this anymore. Tag #993.
* Add nullcheck for frames in FindNearestCommonAncestorFramewolfbeast2019-02-18-0/+4
| | | | This resolves #978.
* Merge branch 'master' of https://github.com/MoonchildProductions/UXPwolfbeast2019-02-03-433/+574
|\
| * issue #908 - implement missing parts of CSS maskyami2019-02-02-433/+574
| |
* | Remove NS_IMPL_CYCLE_COLLECTION_TRAVERSE_SCRIPT_OBJECTSwolfbeast2019-01-18-14/+0
|/
* Telemetry: Remove stubs and related codeadeshkp2019-01-12-195/+0
|
* Make MAX_CSS_VAR_LENGTH unsigned to avoid warnings.wolfbeast2019-01-04-1/+1
| | | | Follow-up for #891. Tag #457.
* Remove AndroidMediaDecoder and friendstrav902018-12-16-9/+0
| | | | They are no longer supported and don't work with newer Android versions anyway.
* Avoid useless FrameNeedsReflow call.wolfbeast2018-12-13-0/+3
|
* Only disallow lazy frame construction for direct children of display: ↵trav902018-12-09-6/+34
| | | | contents elements
* Limit the CSS string length for resolved variables to sane values.wolfbeast2018-12-01-0/+9
| | | | This resolves #891
* Make sure we remove our RefreshDriver observers in CompleteAsyncScroll.wolfbeast2018-11-02-2/+12
| | | | Follow-up to fdbac095968bc952fec6a03765a7156940ae4733
* Ensure that the scroll frame deregisters its refresh driver observers ↵wolfbeast2018-10-31-22/+30
| | | | | | (mAsyncScroll & mAsyncSmoothMSDScroll) before it's destroyed. Tag #345
* [css-grid] Reftests for 88671bcc3633af5a5e34715518e0804ca892fac7JustOff2018-10-20-0/+348
|
* [css-grid] Don't shrink-wrap the inline size when we have an available size ↵JustOff2018-10-20-3/+5
| | | | when measuring block size
* Use device pixels instead of CSS pixels for table borders.wolfbeast2018-10-07-38/+41
| | | | This resolves #821 (regression).
* Make caret width normal/thick behind CJK char configurable.wolfbeast2018-10-07-1/+7
| | | | Fixes #820 (regression).
* Clean up a number of unused variables.wolfbeast2018-09-29-6/+0
| | | | Tag #21.
* Fix wrong SVG sizes with non-integer values for viewBox width/height.wolfbeast2018-09-14-4/+5
| | | | Includes a standalone reftest.
* Bug 1470260 - Part 2: Make RefreshDriverTimer ref-counted and hold a strong ↵wolfbeast2018-09-10-20/+21
| | | | ref on it on the stack when nsRefreshDriver::Tick can be reached.
* Bug 1470260 - Part 1: Ensure that 'this' stays alive for the duration of the ↵wolfbeast2018-09-10-0/+4
| | | | TickRefreshDriver call.
* Bug 1357432 (#750)Moonchild2018-09-05-17/+60
| | | | | | | | | | | | | | | | | | | | | | | | | | | * Part 1. Move IsLocalRefURL to nsContentUtils to reuse this function. (port-rewrite) `IsLocalRefURL` is originally designed to be used by URLValue only. Since we need this function in SVGUseElement::LookupHref too, move it to nsContentUtils as a util function. * Revert "Part 1. Move IsLocalRefURL to nsContentUtils to reuse this function. (port-rewrite)" This reverts commit 19f010c62022e269f99066a8d90e3522fe31adaf. * Part 1. Duplicate IsLocalRefURL to nsContentUtils to reuse this function. `IsLocalRefURL` is originally designed to be used by URLValue only. Since we need this function in SVGUseElement::LookupHref too, duplicate it to nsContentUtils as a util function. This is a duplication because CSSValue uses stringbuffers and not nsStrings. While Bug 1356060 - "Just use nsString in URLValueData" converts this use from stringbuffer to nsString, it builds on a bunch of vartype refactoring (nsString vs. nsAString, etc.) which is too much of a headache to deal with just to deduplicate this simple function. * Part 2. Implement nsSVGEffects::GetBaseURLForLocalRef to export local-ref-url-resolving logic. ResolveURLUsingLocalRef is designed to be internally used by nsSVGEffects::Get-{SVGEffect}-URI functions. Since we also need it in SVGUseElement::LookupHref, make it public in nsSVGEffects. * Part 3. Resolve local-ref in SVGUseElement::LookupHref by nsSVGEffects::GetBaseURLForLocalRef. * Part 4. Reftest for using local-ref as xlink:href value.
* Remove all C++ telemetry autotimerswolfbeast2018-09-04-9/+2
|
* Remove all C++ Telemetry Accumulation calls.wolfbeast2018-09-03-91/+0
| | | | | This creates a number of stubs and leaves some surrounding code that may be irrelevant (eg. recorded time stamps, status variables). Stub resolution/removal should be a follow-up to this.
* Sync disabled state of number control regardless of appearance.wolfbeast2018-08-29-2/+2
|
* Avoid using memset on a not-trivial type like nsTabSizestrav902018-08-18-1/+6
| | | | | | nsTabSizes is non-trivial only because of the user-defined constructor. The idea desired here is certainly to zero all the members without listing them -- but the very act of doing so with a user-defined constructor, makes the idea impossible. Arguably this is something that is permissible in the language, and that the warning should be tailored to permit. I don't think this falls afoul of any of the issues flagged in https://gcc.gnu.org/ml/gcc-patches/2017-06/msg01527.html for example. In the meantime, just explicitly zeroing the three member fields is easy and fixes the warnings.
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-08 12:22:36 +0000