summaryrefslogtreecommitdiffstats
path: root/dom
Commit message (Collapse)AuthorAgeLines
* Issue #1224 - Remove constant expressions from /domMoonchild2020-09-17-57/+54
| | | | | This excludes DOMProxy handlers in dom bindings because that's intertwined with codegen and js that needs to be handled together.
* Issue #1653 - Part 1: Remove WinUtils::SHGetKnownFolderPathMoonchild2020-09-17-3/+3
| | | | | Instead of doing the whole dll-load, replace function dance, we can just use the shlobj.h version of Windows.
* Issue #1643 - Part 4: Hook up all the plumbing.Moonchild2020-09-16-2/+41
|
* Issue #1643 - Part 3: Implement ResizeObserverControllerMoonchild2020-09-16-0/+365
|
* Issue #1643 - Part 2: Implement ResizeObserver APIMoonchild2020-09-16-0/+615
| | | | Implements ResizeObserver, ResizeObserverEntry and ResizeObservation
* Issue #1643 - Part 1: Add GetNodeDepth() to nsContentUtils.Moonchild2020-09-16-0/+22
|
* Merge branch 'es-modules-work'Moonchild2020-09-08-23/+100
|\
| * Issue #618 - Clear the module map when changing a Document's global and addMoonchild2020-09-08-0/+14
| | | | | | | | release build assertions for mismatching compartments.
| * Issue #618 - Make ES6 modules work for resource: URIsMoonchild2020-09-08-1/+23
| |
| * Issue #618 - Implement preloading of module scripts.Moonchild2020-08-27-22/+63
| | | | | | | | This hooks up module scripts to the existing preload mechanism.
* | Issue #1587 followup - Improve resilience of AbortSignals.Moonchild2020-08-28-2/+9
| |
* | [DOM] Only construct JS-implemented objects if inner window is current.Kris Maglione2020-08-28-1/+6
| |
* | [media] Only include source error details in debugging scenarios.Moonchild2020-08-28-1/+13
|/ | | | | | | Unless a user is debugging media errors, this detail is unnecessary to report and could include sensitive data which could be abused by third-party requesters. This aligns it with the standard success/error paradigms in normal browsing situations.
* Issue #618 - Don't preload nomodule scripts when modules are enabledGaming4JC2020-08-26-5/+16
| | | | Ref: BZ 1382020
* Issue #618 - (async) Implement async attribute for inline module scripts.Moonchild2020-08-25-40/+72
| | | | | | | | | | This commit does several things: - Moves the pref check from ScriptLoader to ns[I]Document so it can be called on the document. - Changes the atrribute freezing function to a better name that takes the document as a parameter. - Sets the proper async/defer attributes on HTML script elements based on keywords and whether they are module scripts or not.
* Issue #618 - (async) Keep track of script modes in a single mode state.Moonchild2020-08-25-17/+61
| | | | | | This simplifies handling of combinations of async/defer by assigning one and only one state to scripts. If async then always async > if defer or module then defer > otherwise blocking.
* Issue #618 - (async, preload) Correctly pass info about async/defer to parser.Moonchild2020-08-24-3/+15
| | | | | | This makes sure we don't block body-referred sub-resources by head-referenced defer and async scripts. This is important for all script loads, not just modules, but is added here because it was run into while implementing modules.
* Issue #618 - (async) Split out function to add async request.Moonchild2020-08-24-23/+31
|
* Issue #618 - Rename some script load request flags to be more descriptive.Moonchild2020-08-24-11/+11
|
* Issue #618 - Make document.currentScript null in modules.Moonchild2020-08-23-4/+7
| | | | Because the spec says so.
* Issue #618 - Fix processing of non-parser-generated module scripts.Jon Coppeard2020-08-22-23/+32
|
* Issue #618 - Handle errors for inline module scripts and ensure we update theJon Coppeard2020-08-22-12/+18
| | | | module map after fetch errors.
* Issue #618 - Split SRI verification out from OnStreamComplete.Moonchild2020-08-22-19/+35
|
* Issue #618 - Split handling of load errors out from OnStreamComplete.Moonchild2020-08-22-59/+67
|
* Issue #618 - Integrity for descendant module scripts should be the empty stringMoonchild2020-08-22-4/+4
| | | | Because the spec says so.
* Issue #618 - Don't mute errors for module scripts because they always use CORSJon Coppeard2020-08-22-4/+4
|
* Merge branch 'master' into es-modules-workMoonchild2020-08-22-32/+89
|\
| * Follow up to eb28b1f32 - Correct inputmethod build file by putting ↵Matt A. Tobin2020-08-19-1/+2
| | | | | | | | | | | | Keyboard.jsm back in EXTRA_JS_MODULES JSMs are NOT Components.
| * Merge pull request #1632 from athenian200/link_element_disabledMoonchild2020-08-18-31/+87
| |\ | | | | | | Respond to disabled attribute set on <link> elements from HTML
| | * Fix nitsathenian2002020-08-14-3/+3
| | |
| | * Issue #1629 - Part 3: Implement behind preference.athenian2002020-08-14-7/+18
| | | | | | | | | | | | | | | | | | This is not very "clean," and is mostly done in the same sloppy way as Emilio did it because that's basically the only way you can do it. Note well that this does NOT actually turn off everything I've done in a clean fashion like ifdefs would. For instance, the Explicitly Enabled flag is still present, but is now always false because the only condition that can set it true is behind the pref and therefore inert when this pref is off. Also, because the arguments of SetDisabled have changed, my modifications to SetMozDisabled must be present regardless of whether the pref is on or off. What I have done is turn off the actual reflection of the disabled attribute in Disabled and SetDisabled, as well as in AfterSetAttr. However, turning the pref off seems to restore more or less our old behavior, though there may be subtle differences unlike with an ifdef since this is, unfortunately, not an exact science and I can only turn off changes that happen within individual functions and not changes in how functions interact with each other.
| | * Issue #1629 - Part 2: Implement the Explicitly Enabled flag.athenian2002020-08-13-18/+51
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This part of the bug was significantly complicated by the following major refactors: https://bugzilla.mozilla.org/show_bug.cgi?id=1456435 https://bugzilla.mozilla.org/show_bug.cgi?id=1459498 As best as I can tell, we just need to implement the explicitly enabled flag on every instance of GetStyleSheetInfo, make sure aIsExplicitlyEnabled is false in every situation except the one where the disabled content attribute is removed from a link element, and enable alternate stylesheets if this flag is set on them. So we take the explicitly enabled flag as an input to PrepareSheet, and also add it to LoadStyleLink and LoadInlineStyle. I also decided not to defer loading of alternate stylesheets that have been explicitly enabled.
| | * Issue #1629 - Part 1: Implement basic logic in HTMLLinkElement.athenian2002020-08-13-12/+24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | So basically, I'm trying to adapt this to UXP: https://bugzilla.mozilla.org/show_bug.cgi?id=1281135 The earliest source of difficulty while adapting Bug 1281135 to our codebase was simply getting the new ErrorResult flag added to the SetDisabled function to play nice with the SetMozDisabled function. At this point, the implementation can actually have a stylesheet be disabled by default but there are supposedly issues with alternate stylesheets. At first I played around with the return type of SetMozDisabled to no avail, but I found another solution fairly quickly. https://bugzilla.mozilla.org/show_bug.cgi?id=846972 https://bugzilla.mozilla.org/show_bug.cgi?id=1157898 Essentially, the way around the problem of the number of return arguments not matching up is to declare a local variable within SetMozDisabled called ErrorResult rv, and using that to store the return value of the ErrorResult argument from SetDisabled. After that, because ErrorCode was removed, you would return rv.StealNSResult() in order to report success or failure to any consumer that calls on SetMozDisabled.
* | | Issue #618: Pass down referrer and referrer policy when fetching modules.Moonchild2020-08-13-25/+42
| | | | | | | | | | | | Because the spec says so.
* | | Issue #618: Ignore 'event' and 'for' attributes for module scripts.Moonchild2020-08-13-23/+30
| | | | | | | | | | | | Because the spec says so.
* | | Merge branch 'master' into es-modules-workMoonchild2020-08-13-668/+200
|\| |
| * | Merge pull request #1613 from RealityRipple/AspectRatioMoonchild2020-08-08-17/+52
| |\ \ | | | | | | | | [Image/CSS] Intrinsic Aspect Ratio
| | * | Issue #1620 - Enable Intrinsic Ratio by DefaultAndy2020-08-07-1/+1
| | | | | | | | | | | | | | | | A simpler name feels so much cleaner.
| | * | Issue #1620 - Remove Development CommentsAndy2020-08-07-2/+0
| | | |
| | * | Issue #1620 - Use Intrinsic Aspect Ratio for ImagesAndy2020-08-04-17/+54
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | https://bugzilla.mozilla.org/show_bug.cgi?id=1547231 https://bugzilla.mozilla.org/show_bug.cgi?id=1559094 https://bugzilla.mozilla.org/show_bug.cgi?id=1633434 https://bugzilla.mozilla.org/show_bug.cgi?id=1565690 https://bugzilla.mozilla.org/show_bug.cgi?id=1602047 Make use of Aspect Ratios in Image frames before Images are loaded. - Check for width and height HTML properties and create a ratio with them. - Overwrite HTML size values with actual image dimensions on load. - Collapse any frames with srcless images. Comments: dom/html/nsGenericHTMLElement.cpp:1483 layout/generic/nsImageFrame.cpp:289
| * | | Pref and disable getRootNode()Moonchild2020-08-07-1/+1
| |/ / | | | | | | | | | | | | | | | | | | This is apparently used for fallback selection and if available it is "assumed" Shadow DOM is also available, while this is a utility function. Webcompat is a nightmare sometimes.
| * | [dom] Fix a spec compliance issue with the HTML LS regarding script loading.Moonchild2020-07-29-7/+9
| | | | | | | | | | | | This fixes a spec compliance issue with section 8.1.4.2 Fetching scripts.
| * | [network/dom] Improve sanitization of download filenames.Moonchild2020-07-29-0/+8
| | |
| * | Issue #1391 - Remove the DOM battery APIMoonchild2020-07-28-613/+0
| | |
| * | Fix line endings.Moonchild2020-07-25-714/+714
| | |
| * | Issue #1587 Part 12 (followup 2): Allow clearing of signal by setting to null.Moonchild2020-07-25-2/+7
| | |
| * | Issue #1587 Part 11 (followup 1): Implement multithreaded signals for workers.Moonchild2020-07-24-728/+823
| |/
| * Issue #618 - Remove eager instantiation - Debug follow upGaming4JC2020-07-11-1/+2
| | | | | | | | | | | | | | The added debug assertion did not take into account microtask refactoring done in BZ 1405821. Resulting in error: no member named 'IsInMicroTask' in 'nsContentUtils'. This resolves the error.
* | Issue #618 - Simplify module resolve hook to be a function pointerMoonchild2020-08-06-31/+19
| | | | | | | | | | This is an ahead-of time port to try and address #1624. This is based on BZ 1461751 and Jon Coppeard's work in it.
* | Issue #618 - Keep track of which modules in a graph have been fetched using ↵Gaming4JC2020-08-04-72/+92
| | | | | | | | | | | | a visited set Ref: BZ 1365187
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-01 03:29:17 +0000