summaryrefslogtreecommitdiffstats
path: root/dom
Commit message (Collapse)AuthorAgeLines
* Use meaningful error message in URLSearchParams::ConstructorJustOff2019-03-14-1/+1
|
* Align IDL record to C++ conversion with the spec when Symbol-named ↵JustOff2019-03-13-5/+3
| | | | properties are involved
* Construct URLSearchParams from record<>JustOff2019-03-13-4/+10
|
* Construct URLSearchParams from sequence or from stringJustOff2019-03-13-43/+24
|
* Implement the spec provision for handling repeated keys in records by ↵JustOff2019-03-13-9/+46
| | | | updating the existing value
* Actually change the key type of a record, and its corresponding conversion ↵JustOff2019-03-13-11/+41
| | | | behavior, depending on what the IDL says
* Rename MozMap.h to Record.hJustOff2019-03-13-0/+0
|
* Add ConvertJSValueTo*String functions that just take a value and hand out a ↵JustOff2019-03-13-8/+34
| | | | string, without extra complications
* Rename the MozMap C++ type to "record" and give it a template parameter for ↵JustOff2019-03-13-126/+145
| | | | the key type
* Rename "MozMap" to "record" in our IDL parser and IDL filesJustOff2019-03-13-78/+83
|
* Split up PrimitiveOrStringType into PrimitiveType and StringType in the Web ↵JustOff2019-03-13-24/+36
| | | | IDL parser
* Change JS to MozMap conversion to more closely follow the record<> specJustOff2019-03-13-6/+24
|
* Add some tests for distinguishability of unionsJustOff2019-03-13-2/+4
|
* Disallow mozmap-typed constantsJustOff2019-03-13-0/+3
|
* Fix up some minor issues with default value handling in codegenJustOff2019-03-13-5/+9
|
* Change the MozMap API and data storage to more what we want record<> to look ↵JustOff2019-03-13-103/+55
| | | | like
* Support string default values for unions containing USVStringJustOff2019-03-13-1/+3
|
* Merge pull request #995 from MoonchildProductions/httpaccept-workMoonchild2019-03-12-14/+0
|\ | | | | Change the way http Accept: headers are used.
| * Remove various hard-coded Accept: headerswolfbeast2019-03-07-14/+0
| | | | | | | | | | | | | | Since we're now handling this in the network back-end, there's no need for this anymore. Tag #993.
* | Prevent loading of document subresources over FTP.wolfbeast2019-03-09-0/+59
|/
* Preserve newlines in textarea placeholdersJustOff2019-02-19-1/+5
|
* Implement origin-clean algorithm for ImageBitmap.wolfbeast2019-02-14-60/+143
| | | | This resolves #973.
* Remove WebExtension support from the platform.wolfbeast2019-02-13-109/+0
| | | | | | - Conditional code - WE APIs - WE toolkit theming
* Allow empty string on `location.search` setter.wolfbeast2019-02-12-4/+0
| | | | Fixes #970.
* Revert "Increase purple limit triggers for CC."wolfbeast2019-02-07-2/+2
| | | | This reverts commit babedf6c696f88734e59b63d0c6614962cc57519.
* Get RefPtr to transaction before using it. (DiD)wolfbeast2019-02-07-1/+3
| | | | | Avoid potential use-after-free by getting a RefPtr to a transaction before calling content code that could cause its de-allocation.
* Increase slice time for longer running CCs.Andrew McCreight2019-01-29-3/+14
| | | | | | | | | If a CC takes too long (around 50 slices) or gets interrupted by a GC, we have to finish it synchronously, which can cause a big pause. This patch tries to avoid that by eagerly increasing the slice budget the longer a CC goes on. It linearly increases the slice time from 5ms to 40ms as we approach the halfway point of a CC (1 second), matching GC pauses, and then leaves it at 40ms.
* Increase purple limit triggers for CC.wolfbeast2019-01-29-2/+2
| | | | | Making these much larger to allow more purple buffer buildup and prevent overzealous cycle collection on purple buffer pressure.
* Merge branch 'master' into cycle_collector-workwolfbeast2019-01-29-2/+12
|\
| * Properly camelCase dom.intersectionObserver.enabled pref.wolfbeast2019-01-19-2/+2
| |
| * Actually unlink targets from registered intersection observers.wolfbeast2019-01-19-0/+10
| | | | | | | | | | | | | | When a node is released/removed, and it has an intersection observer attached to it, that observer should be unlinked at the time of release. This resolves #935.
* | Remove NS_IMPL_CYCLE_COLLECTION_TRAVERSE_SCRIPT_OBJECTSwolfbeast2019-01-18-96/+1
| |
* | Consolidate tracing and traversing.wolfbeast2019-01-18-1/+1
|/
* Rewrite IntersectionObserver list handling to be more robust.wolfbeast2019-01-18-8/+40
| | | | Tag #935.
* Add isIntersecting property to IntersectionObserverEntry.wolfbeast2019-01-17-0/+11
| | | | | | Per updated spec. This resolves the issue raised in #249.
* Remove unused telemetry timer from HTMLMediaElement.hadeshkp2019-01-14-7/+0
|
* Telemetry: Remove stubs and related codeadeshkp2019-01-12-1160/+25
|
* Align Element.ScrollIntoView() with the spec.wolfbeast2019-01-08-25/+56
| | | | | | | This also removes the (unused) shadow alias from nsIDOMHTMLElement which used the different calling convention. This resolves #927
* Remove proprietary constructor on AudioContext.wolfbeast2019-01-04-33/+1
| | | | | | | | | This is a B2G leftover, was proprietary, and is causing issues because `AudioContext` can now have a parameter that is a property bag, per spec (we do not do anything with the property bag now; the audio back-end will use automatic values for everything). This resolves #924.
* Avoid redefined macro warning in MediaFormatReadertrav902018-12-31-0/+4
|
* [FFmpeg] Don't define AV_CODEC_ID_VPx with libavcodec 58trav902018-12-28-3/+6
|
* [FFmpeg] Use new decode API with recent FFmpeg version.trav902018-12-28-7/+66
| | | | In libavcodec 58 and later, the old avcodec_decode_video2 is broken and only return the first visible frame found after a VP9 super-frame.
* Fix crashiness of IntersectionObservers.wolfbeast2018-12-24-21/+25
| | | | Mozilla hashtables -still- suck.
* [intersection-observer] Calculate areas using int64_t.wolfbeast2018-12-22-4/+6
| | | | Tag #249
* Fix singed/unsigned type confusion for intersection threshold.wolfbeast2018-12-22-3/+3
| | | | Tag #249
* Use content area as the intersection rectangle ...wolfbeast2018-12-22-7/+11
| | | | | ... for custom root with overflow clip. Tag #249
* Map intersectionRect to the coordinate space of the target document.wolfbeast2018-12-22-7/+8
| | | | | | Spec says: "Map intersectionRect to the coordinate space of the viewport of the Document containing the target." Tag #249
* Use targetFrame->GetRectRelativeToSelf() as the initial intersection rect.wolfbeast2018-12-22-1/+1
| | | | Tag #249.
* Intersection ratio should be 1.0 for zero-area intersections.wolfbeast2018-12-22-1/+7
| | | | Tag #249
* Revise lifetime management of IntersectionObservers.wolfbeast2018-12-22-26/+46
| | | | Tag #249