| Commit message (Collapse) | Author | Age | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.)
|
|
|
|
| |
For clarity and to prevent typoes.
|
|
|
|
| |
This doesn't solve the blurriness yet, but is part of the problem.
|
|
|
|
| |
This doesn't solve the blurriness yet, but is part of the problem.
|
|
|
|
| |
No code changes.
|
|
|
|
|
|
|
|
|
| |
Tag #1052 (backout).
Backed out for creating issues like #1191 and other issue-less problems
with e.g. losing the caret from text boxes. Of note: this was also
backed out from m-c for similar reasons in Bug 1332433.
This fixes #1191.
This reverts commit 3424afccaebc71c4acd4fa9eadf519c408c5965b.
|
|
|
|
|
|
|
|
|
|
| |
https://bugzilla.mozilla.org/show_bug.cgi?id=1373884
Fixes comments for Frameproperties.
These comments went unnoticed earlier.
No code changes.
|
|
|
|
|
|
| |
we have
Look into optimizing out the hashtable lookups from nsContainerFrame
|
|
|
|
|
|
|
|
|
|
|
| |
UXP has:
MOZ_RELEASE_ASSERT(sAliveDisplayItemDatas && sAliveDisplayItemDatas >Contains(this));
sAliveDisplayItemDatas->RemoveEntry(this);
and this gets hit during frame destruction.
Combine these checks.
|
|
|
|
| |
Dispense the shared hashtable and instead attach the frame property list directly to nsIFrame.
|
|
|
|
| |
This reverts commit e69b3f567c4b8957cc09ba4359e84939f77781c5.
|
| |
|
|
|
|
|
|
|
|
| |
* 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
|
|\
| |
| | |
nsFrameList::GetLength() calls in nsDisplayListBuilder::MarkFramesForDisplayList() are slow
|
| | |
|
| | |
|
|/ |
|
|
|
|
| |
Tag #1052
|
| |
|
|
|
|
| |
also be zero
|
|
|
|
| |
This resolves #978.
|
| |
|
| |
|
|
|
|
| |
contents elements
|
|
|
|
| |
Fixes #820 (regression).
|
|
|
|
| |
Tag #21.
|
|
|
|
| |
ref on it on the stack when nsRefreshDriver::Tick can be reached.
|
|
|
|
| |
TickRefreshDriver call.
|
| |
|
|
|
|
|
| |
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.
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
This resolves #626
|
| |
|
|
|
|
|
| |
- Conditionals and code blocks. (MOZ_ENABLE_PROFILER_SPS)
- Stub out several profiler-only functions.
|
|
|
|
|
|
| |
firing onload in nsDocumentViewer::LoadComplete
Issue #357
|
|
|
|
|
|
| |
pixel ratio is set to its current value
Issue #357
|
|
|
|
| |
Tag #288
|
| |
|
|
|
|
| |
completely and use ICU.
|
|
|
|
|
| |
https://github.com/MoonchildProductions/moebius/pull/146
https://github.com/MoonchildProductions/Pale-Moon/pull/1400
|
|\
| |
| | |
CSS - implement text-justify property
|
| | |
|
| |
| |
| |
| | |
https://github.com/MoonchildProductions/moebius/pull/138
|
| |
| |
| |
| | |
https://github.com/MoonchildProductions/moebius/pull/195
|
| |
| |
| |
| | |
https://github.com/MoonchildProductions/moebius/pull/71
|
| |
| |
| |
| |
| |
| |
| | |
Round subpixel border widths to nearest integer instead of nearest-below integer.
Split caret widths off from border widths and continue to use rounding to nearest-below integer for that.
Bump Goanna version for visual rendering change.
|
|\|
| |
| |
| | |
html_input_datetime_1
|
| |
| |
| |
| |
| |
| |
| |
| | |
function. r=jwatt, a=RyanVM
--HG--
extra : source : 86d41b5efe074f6988085082df9ef537eee0813a
extra : intermediate-source : ea406489f93a0a8fa05ff568acdff07ce6b118c4
|
| | |
|
| |
| |
| |
| | |
with an intrinsic ratio
|