| Commit message (Collapse) | Author | Age | Lines |
|
|
|
|
|
|
|
| |
On MacOS, particularly large allocations within the platform limits
(1.2G+) will fail and crash. This adds a specific size check for that
when working around driver bugs (default).
While there, added a generic size_t limited size check for the
platform, and reporting OOM if too large.
|
| |
|
|
|
|
|
| |
No longer follow the value's prototype chain when creating index updates
in IndexedDB.
|
|
|
|
|
|
|
| |
This also addresses clearing of document dependent JS slots which might
get out of sync with innerWindow navigation; relevant comments added.
This resolves #1253
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
| |
nsXMLContentSerializer::CheckElementEnd so that we can properly
determine whether it has children.
This resolves #1221
|
|\
| |
| | |
Convert dom/base/nsImageLoadingContent.cpp to use AsyncOpen2 and followups along with it (1445670 and 1373780 part 2 and 3)
|
| |
| |
| |
| |
| |
| | |
along with it (1445670 and 1373780 part 2 and 3)
Convert dom/base/nsImageLoadingContent.cpp to use AsyncOpen2 and followups along with it (1445670 and 1373780 part 2 and 3)
|
|/ |
|
|\
| |
| | |
Issues #816 / #802 - SpiderMonkey Tuneup
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
Wrapper::Renew.
|
| |
| |
| |
| |
| |
| |
| | |
Specifically, three changes:
1) valueOf should be non-enumerable.
2) valueOf should be === to Object.prototype.valueOf.
3) There should be no toJSON.
|
| | |
|
| |
| |
| |
| |
| | |
We already don't allow cross origin POST redirects on 307 redirects;
this adds extra guards to make sure we don't allow them on 308s either.
|
| | |
|
|/ |
|
|\
| |
| | |
Add support for AAC audio in matroska/webm files
|
| |\ |
|
| | |
| | |
| | |
| | | |
Allow CRC32 elements in matroska cluster elements.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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.
|
| | | |
|
| | |
| | |
| | |
| | | |
to background.
|
| | |
| | |
| | |
| | |
| | | |
This patch also makes UDPSocketChild::Bind return NS_ERROR_NOT_AVAILABLE
when mBackgroundManager is null.
|
|\ \ \
| |_|/
|/| | |
Dispatch a PluginRemoved event for actual plugins, not images/unknown/iframe-type <objects>
|
| |/
| |
| |
| |
| |
| |
| |
| | |
images/unknown/iframe-type <objects>
If a page uses or removes many <object> elements which are not actually plugins, loading the page goes to a crawl because UXP recalculates the plugin UI every time.
Only dispatch a PluginRemoved event for actual plugins.
|
| |
| |
| |
| |
| | |
- Allow "Save As..." downloads
- Allow subresource use if the top-level document is also on FTP
|
|/ |
|
| |
|
|
|
|
| |
Allow avc (h.264) content in matroska/webm containers
|
|
|
|
| |
Dispense the shared hashtable and instead attach the frame property list directly to nsIFrame.
|
|
|
|
|
|
| |
starting in e10s mode.
This resolves #1130
|
|
|
|
|
| |
- Instead of trying the failing refactored Mozilla way, simply add a
check where needed building on what was put in place previously.
|
|
|
|
| |
This reverts commit e69b3f567c4b8957cc09ba4359e84939f77781c5.
|
|
|
|
|
|
| |
Some drivers on Linux are not supportive of very large allocation sizes
(esp. applicable to Linux x86 builds of UXP applications) and could
cause issues. Treat this the same way we already do on Mac/Darwin.
|
| |
|
| |
|
|\
| |
| | |
NodeInfoManager should use a local cache
|
| |
| |
| | |
issue #1111
|
| |
| |
| |
| |
| | |
- Structure the code better
- Directly downmix to mono from multichannel
|
|/
|
|
|
|
|
|
|
|
| |
Normally we wouldn't need to send any notifications if the actor was
already destroyed, but it can be a VersionChangeOp which needs to
notify its parent operation (OpenDatabaseOp) about the failure.
So SendFailureResult needs to be called even when the actor was
destroyed. Normal operations redundantly check if the actor was
destroyed in SendSuccessResult and SendFailureResult, therefore it's
ok to call it in all cases here.
|