summaryrefslogtreecommitdiffstats
path: root/dom
Commit message (Collapse)AuthorAgeLines
...
| * 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
* | Issue #618 - Simplify module map interfaceGaming4JC2020-08-04-14/+14
| | | | | | | | Ref: BZ 1365187
* | Issue #618 - Remove eager instantiation - Debug follow upGaming4JC2020-08-03-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 - Record module dependency before starting fetch so that errorJon Coppeard2020-08-02-1/+1
| | | | | | | | | | | | handling works correctly Ref BZ 1395896
* | Issue #618 - Align error handling for module scripts with the spec (again)Moonchild2020-07-08-58/+79
| | | | | | | | | | | | | | | | This updates module implementation to match spec regarding handling of instantiation errors, after it was changed yet again, this time to not remember instantiation errors, but instead immediately rethrow applicable ones. Ref: BZ 1420420
* | Issue #618 - Fix error events fired when loading JS module dependencies failMoonchild2020-07-08-9/+12
|/ | | | | | | When module dependencies fail, don't spam with errors for each import; only fire the error event once. Ref: BZ 1421259
* Issue #618 - Slightly improve module scripting tests.Moonchild2020-07-04-16/+44
| | | | Ref: BZ 1388728
* Issue #618 - Further align error handling for module scripts with the specMoonchild2020-07-04-89/+280
| | | | Ref: BZ 1388728
* Issue #618 - Remove eager instantiationMoonchild2020-07-04-129/+10
| | | | | This backs out the stuff added in Bug 1295978. Ref: BZ 1295978, 1388728
* Issue #618 - Match JSAPI names with the changes in ↵Moonchild2020-07-03-12/+12
| | | | | | 9ca74147225eed305e28c7887f9b2251aeeb0f36 Ref: BZ 1388728
* Issue #618 - Add clarifying code comments.Moonchild2020-07-01-0/+12
|
* Issue #618 - Check for failed instantiation when starting to fetch dependenciesMoonchild2020-07-01-0/+6
| | | | | If instantiation has failed, then also fail the load and don't fetch imports. Ref BZ: 1358882
* Issue #1603 - Part 2: Split some classes out of ScriptLoader.cppMoonchild2020-07-01-534/+651
| | | | | | | This splits ScriptLoader up the same way Mozilla did with the exception of ScriptRequest due to the fact that ScriptLoader and ScriptRequest are interdependent and would create a circular dependency if split apart when not using unified building.
* Issue #1603 - Part 1: Reorganize ScriptLoader/ScriptElementMoonchild2020-06-30-499/+539
| | | | | | - Moves scripting parts of DOM into 'dom/script' - Renames nsScript{Loader/Element} to Script{Loader/Element} - Adjusts all callers
* Issue #1602 - Make sure we have a JSObject before trying to get global.wolfbeast2020-06-27-1/+7
| | | | | | | | Dynamic script loading/unloading (thank you modules) can yank the script out from under us before the JS API for it is initialized, leading to null deref crashes. This adds a simple check if the passed-in object is sane and present. Resolves #1602
* Bug 1430299 - Add DocumentOrShadowRoot interfaceMatt A. Tobin2020-06-13-6/+31
| | | | Tag #1375
* Bug 1429656 - Implement ShadowRoot.activeElementMatt A. Tobin2020-06-13-17/+88
| | | | Tag #1375
* Bug 1426494 - Share more code between nsIDocument and ShadowRootMatt A. Tobin2020-06-13-335/+368
| | | | Tag #1375
* Bug 1355787 - nsIdentifierMapEntry should let one to use either strings or ↵Matt A. Tobin2020-06-13-22/+76
| | | | | | atoms as keys to avoid slow string assignments when possible. Tag #1375
* Bug 1217436 - Make nsIdentifierMapEntry::mIdContentList an AutoTArray to ↵Matt A. Tobin2020-06-13-4/+12
| | | | | | save an allocation Tag #1375
* Merge branch 'abortcontroller-work'Moonchild2020-06-12-43/+1378
|\
| * Issue #1587 - Part 9: Immediately reject an already-aborted signalMoonchild2020-06-12-1/+6
| |
| * Issue #1587 - Part 8: Remove controller follow/unfollowMoonchild2020-06-12-124/+1
| | | | | | | | Since it didn't end up being in the final spec after all.
| * Issue #1587 - Part 7: Rename FetchController to AbortControllerMoonchild2020-06-11-142/+142
| | | | | | | | | | Also renames FetchSignal to AbortSignal. Includes renaming the various controlling prefs to enable.
| * Issue #1587 - Part 6: Move FetchController/Signal to its own dirMoonchild2020-06-11-7/+41
| | | | | | | | Since it is specced separately from fetch.
| * Issue #1587 - Part 5: Hook FetchObserver up to the Fetch APIMoonchild2020-06-11-75/+399
| |
| * Issue #1587 - Part 4: Implement FetchObserverMoonchild2020-06-11-0/+223
| |
| * Issue #1587 - Part 3: Hook FetchSignal up to the Fetch APIMoonchild2020-06-10-30/+292
| |
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-10 02:41:05 +0000