summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeLines
* Issue #1230 - Part 3: Update ReftestsGaming4JC2019-09-28-122/+143
| | | | | Ref: 1434478 part 7 - Update tests and enable some previously temporarily disabled Grid reftests from bug 1427608.
* Issue #1230 - Part 2: Align devtools to the changes in css-gridGaming4JC2019-09-28-2/+4
| | | | | Ref: 1398537 part 4 - [css-multicol] Implement percentages for 'column-gap' (automated update of devtools).
* Issue #1230 - Part 1: Fix Back-computing percentages for intrinsic sizing in ↵Gaming4JC2019-09-28-319/+240
| | | | | | | | | | | | | | | | | | | | | | 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.)
* Issue #1233 - Part 2: Update ReftestsGaming4JC2019-09-28-145/+4150
| | | | | | | | | | | | | | | | | | List of relevant patches applied: 1425599 part 15 - [css-grid] Test reference fixes + more tests. 1373678 Part 3: Add line number checks to test_grid_implicit.html. 1416350 - Part 3: Add test to verify line numbers of grids with leading implicit tracks. 1416350 - Part 4: Add a reftest of repeat:auto-fit grids with leading implicit tracks. 1417711 - [css-grid] An abs.pos. grid container child that only covers removed 'auto-fit' tracks should not span to the end padding edge. 1416350 - Part 5: Correct the expected results for grids that have leading implicit tracks. 1418727 part 3 - [css-grid] Reftest updates.
* Issue #1233 - Part 1: Fix grid overflow and rendering issues by improving ↵Gaming4JC2019-09-28-293/+410
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Layout CSS-Grid API List of relevant patches applied: 1425599 part 1 - [css-grid] Change the track sizing algorithm for spanning items so that it accumulates individual item contributions to the plan by max() rather than incrementing the planned size directly. Also, fix a bug when copying back the planned limits after updating it for the first span group. It should only copy back track sizes that were actaully spanned by those items, other content-sized tracks' limits should remain at "infinity". 1425599 part 2 - [css-grid] Factor out the min-sizing parts of the track sizing for spanned items to a templated method (idempotent change). 1425599 part 3 - [css-grid] Factor out most of the max-sizing parts of the track sizing for spanned items to a templated method (idempotent change). 1425599 part 4 - [css-grid] Factor out the starting base/limit size to a templated method (idempotent change). 1425599 part 5 - [css-grid] Make CollectGrowable a templated method so that it works with either base/limit sizes (idempotent change). 1425599 part 6 - [css-grid] Make the size distribution methods templated with the intent of merging them in a later patch (idempotent change). This patch also introduces an eInfinitelyGrowable bit to help get rid of the 'limits' temporary track sizes in the next patch. 1425599 part 7 - [css-grid] Remove the 'limits' copy of track sizes since they are no longer needed (idempotent change). 1425599 part 8 - [css-grid] Factor out the fit-content clamping function from DistributeToTrackLimits and pass it as a param instead (idempotent change). 1425599 part 9 - [css-grid] Merge DistributeToTrackLimits/Bases (idempotent change). 1425599 part 10 - [css-grid] Make MarkExcludedTracks a static method since it doesn't use 'this' (idempotent change). 1425599 part 11 - [css-grid] Hoist the marking of excluded tracks out from GrowSelectedTracksUnlimited to a separate method (idempotent change). 1425599 part 12 - [css-grid] Merge CopyPlanToBase/Limits into a templated method instead (idempotent change). 1425599 part 13 - [css-grid] Merge Grow[Base|Limits]ForSpanningItems into a templated method instead (idempotent change). 1425599 part 14 - [css-grid] Use iterators instead of an array + start/end index for the item data (idempotent change). 1425599 part 16 - [css-grid] Make SizeContributionForPhase a template. 1425599 - [css-grid] Follow-up bustage fix for stupid compiler warnings. 1378481 - Assign 'roundingError' in the default branch too, to avoid a maybe-uninitialized compiler warning. 1423292 - [css-grid] Add a couple of ItemState bits to Dump(), and make an ItemState assertion stricter (DEBUG-only changes). 1373678 Part 1: Reduce grid line numbers by count of leading implicit lines, minimum 0. 1416350 - Part 1: Correctly account for removed 'auto-fit' tracks also when there are leading implicit tracks. 1416350 - Part 2: Correct logic for Grid API line numbering with leading implicit tracks. 1418727 part 1 - [css-grid] Introduce StateBitsForRange() that collects the union of the state bits for a range of tracks (idempotent change). 1418727 part 2 - [css-grid] Require that an item spans at least one track with an 'auto' min sizing function for Automatic Minimum Size to apply.
* Merge pull request #1232 from adeshkp/disable-color-mgmt-linuxMoonchild2019-09-24-1/+8
|\ | | | | Issue #1231 - Stop using ICC profiles on Linux.
| * Issue #1231 - Stop using ICC profiles on Linux.adeshkp2019-09-24-1/+8
|/ | | | | General consensus seems to be that color management on Linux desktops is not mature enough to enable by default.
* No issue - Add 360 Safeguard to DLL blocklistMoonchild2019-09-17-0/+3
| | | | | 360 Safeguard/360 Total Security (Qihoo) causes crashes in a11y components. This adds the offending dll to the injection blocklist. See BZ bug 1536227 for details.
* Issue #1226 - Explicitly enable sse2 on x86_64 also.wolfbeast2019-09-10-1/+1
| | | | | | Although it's enabled by default in gcc (should be, anyway!), we're being explicit here for 64-bit x86 platforms here also. This matches the old behavior.
* Don't assume Intel architecture for compiler optimizations on Linux/gcc.wolfbeast2019-09-10-2/+7
| | | | | This only adds SSE2 flags when the CPU architecture is correct for it. Resolves #1226
* Fix whitelisting of JavaScript-uris by CSP hash.wolfbeast2019-09-05-2/+13
|
* Properly implement various HSTS states.wolfbeast2019-09-05-16/+27
| | | | | | | | Previously, HSTS preload list values could be overridden temporarily due to counter-intuitive behavior of the API's removeState function. This adds an explicit flag to the API for writing knockout values to the Site Security Service, with the default resetting to whatever the preload list state is.
* Use the correct group for JIT constraints.wolfbeast2019-09-05-18/+164
| | | | | | | This fixes a rare crash/CTD in JS. This adds information about the constraints to a new RAII class so we can finish all constraints at the end. Based on changes in BZ 1568397
* Ensure the right body element is used throughout the method call.Olli Pettay2019-09-05-3/+3
|
* Add checks to respect CSP-wildcard + Ports.Sebastian Streich2019-09-05-14/+18
|
* Fix a crash in IndexedDB.wolfbeast2019-09-04-39/+102
|
* Kill newly-spawned threads if we're shutting down.Nathan Froyd2019-09-04-1/+3
|
* Remove HTML5 parser java docs and generation code.wolfbeast2019-09-04-20210/+0
| | | | | java->C++ automated translation is not something we want to deal with now or in the future.
* Belatedly fix html5 parser attribution for files not covered by the MPL.wolfbeast2019-09-04-0/+17
|
* Fix an issue with the html5 tokenizer and tree builder.wolfbeast2019-09-04-39/+103
|
* Merge branch 'master' of https://github.com/MoonchildProductions/UXPwolfbeast2019-09-04-4/+8
|\
| * Issue #1217 - Add support for (later versions of) the Windows 10 SDKAscrod2019-09-01-4/+8
| |
* | Correctly return zero vertices if clipping plane 0 or 2 clip away theMarkus Stange2019-09-04-15/+91
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | entire polygon. This fixes a bug that was introduced three years ago in BZ bug 1268854. What happened was that the final pass over the polygon assumed that the current polygon was living in plane[0]. But due to the double buffering, the "current" polygon alternates between plane[0] and plane[1]. The bug had also introduced an early exit so that we could hit the final pass at a time where the current, now empty, polygon was in plane[1]. So we would incorrectly treat all 32 points in plane[0] as part of the final polygon. This bug was responsible for intermittently unreasonable numbers in CompositorOGL's fill rate / overdraw overlay. This fixes a regression caused by the fix for CVE-2016-5252.
* | Revert "Correctly return zero vertices if clipping plane 0 or 2 clip away the"wolfbeast2019-09-04-13/+11
|/ | | | This reverts commit 09a8b2f19689b679b1268a3004ec5e3f37b9732a.
* Merge working copy branchwolfbeast2019-09-01-14/+33
|\
| * Issue #1222: Don't load plugin instances when they have no `src` URI.wolfbeast2019-09-01-0/+17
| | | | | | | | | | | | Favor fallback content in that case (if present). Fallback is always considered "good" in this case so may end up doing nothing which is what we'd want for corner cases that hammer this routine with no content.
| * Correctly return zero vertices if clipping plane 0 or 2 clip away thewolfbeast2019-09-01-11/+13
| | | | | | | | | | | | entire polygon. This fixes a regression caused by the fix for CVE-2016-5252
| * Issue #1179: fix indentationwolfbeast2019-09-01-3/+3
|/
* New cycle version bumpwolfbeast2019-08-28-1/+1
|
* Issue #1221: Pass the original element intowolfbeast2019-08-28-13/+46
| | | | | | | nsXMLContentSerializer::CheckElementEnd so that we can properly determine whether it has children. This resolves #1221
* [MCP Applications] Add %WIDGET_TOOLKIT% to the AUS update url for Pale Moon ↵Matt A. Tobin2019-08-22-4/+2
| | | | | | and Basilisk Also removes the redundant branding version of app.update.url in Pale Moon that was missed when many prefs were merged back into application preferences
* Merge pull request #1212 from Ascrod/xdg-desktop-portalMoonchild2019-08-16-39/+118
|\ | | | | Allow the use of Xdg desktop portal dialogs
| * Issue #999 - Disable native file picker by default.Ascrod2019-08-15-4/+13
| |
| * Issue #999 - Use xdg-desktop-portal for file selection dialogs on Linux.Ascrod2019-08-10-39/+109
| |
* | Issue #1208: Update Sync policies.js getters/setters to prevent race.wolfbeast2019-08-15-15/+55
| |
* | Issue #1208: Remove `services.sync.enabled` pref.wolfbeast2019-08-15-24/+3
| | | | | | | | | | | | | | Sync will not do anything unless specifically set up to do so and at least one engine is enabled, so there's no need for this "master switch" to force it disabled based on engines being disabled (which was its previous function to shortcut syncing in that situation).
* | Issue #1208: Fix jsonLoad in Sync's `util.js` to handle errors.wolfbeast2019-08-15-4/+12
| | | | | | | | | | - `OS.Path.join` can throw, so we always need to try/catch it. - Also do a sanity check to make sure `callback` is defined before use
* | Issue #1124: [Basilisk] Remove Dev Edition theme.wolfbeast2019-08-14-883/+0
| |
* | Issue #1124: [Basilisk] Remove Dev Edition front-end tie-ins.wolfbeast2019-08-14-211/+2
| |
* | Issue #1124: Remove Firefox Developer Edition code.wolfbeast2019-08-14-223/+5
| | | | | | | | Removes all occurrences of MOZ_DEV_EDITION code and some helpers.
* | Update platform version.wolfbeast2019-08-14-1/+1
| |
* | Issue #438: Revert incorrect changes to w3c-css reftestswolfbeast2019-08-14-4/+4
| |
* | Issue #438: Add reftests.wolfbeast2019-08-14-0/+27
| |
* | Issue #438: Make the nsSVGOuterSVGAnonChildFrame a reference frame.wolfbeast2019-08-14-23/+33
| | | | | | | | | | This causes transforms of the <svg> contents to be unaffected by scrolling / offset changes of the <svg> element.
* | Issue #438: Check for non-rectilinear transformswolfbeast2019-08-14-0/+3
| |
* | Issue #438: Add an IsRectilinear helper method to gfxMatrix.wolfbeast2019-08-14-0/+12
| |
* | Issue #438: Rename coord/coords to originValue/transformOrigin.wolfbeast2019-08-14-13/+13
| | | | | | | | For clarity and to prevent typoes.
* | Issue #438: Pixel-snap subpixel value for outer SVG and anon child.wolfbeast2019-08-14-2/+7
| | | | | | | | This doesn't solve the blurriness yet, but is part of the problem.
* | Issue #438: Do not round the translation of an SVG frame.wolfbeast2019-08-14-6/+36
| | | | | | | | This doesn't solve the blurriness yet, but is part of the problem.
* | Issue #1211: Allow the loading of TYPE_FONT from file: URLs.wolfbeast2019-08-14-1/+14
| | | | | | | | | | | | | | This bypasses the CORS restriction of unique file: URLs in the case of fonts loaded through CSS. Resolves #1211.
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-16 16:57:52 +0000