summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
* Issue #1676 - Part 21: Use js-cxxflags.mozbuild in testing code and js shellMatt A. Tobin2020-11-04
|
* Issue #1676 - Part 20: Split vtune sources out of js/src/moz.buildMatt A. Tobin2020-11-04
|
* Issue #1676 - Part 19: Split ctypes sources out of js/src/moz.buildMatt A. Tobin2020-11-04
|
* Issue #1676 - Part 18: Move and separate top level sources from vm sources ↵Matt A. Tobin2020-11-04
| | | | in js/src/moz.build
* Issue #1676 - Part 17: Put remaining source files which have debug code ↵Matt A. Tobin2020-11-04
| | | | ifdef'd behind MOZ_DEBUG
* Issue #1676 - Part 16: Split WASM sources out of js/src/moz.buildMatt A. Tobin2020-11-04
| | | | Also puts WasmBinaryIterator.cpp which is debug code ifdef'd behind MOZ_DEBUG
* Issue #1676 - Part 15: Split threading sources out of js/src/moz.buildMatt A. Tobin2020-11-04
|
* Issue #1676 - Part 14: Split proxy sources out of js/src/moz.buildMatt A. Tobin2020-11-04
|
* Issue #1676 - Part 13: Split perf sources out of js/src/moz.buildMatt A. Tobin2020-11-04
|
* Issue #1676 - Part 12: Split jit sources out of js/src/moz.buildMatt A. Tobin2020-11-04
|
* Issue #1676 - Part 11: Split irregexp sources out of js/src/moz.buildMatt A. Tobin2020-11-04
|
* Issue #1676 - Part 10: Split gc sources out of js/src/moz.buildMatt A. Tobin2020-11-03
|
* Issue #1676 - Part 9: Move DIRS down in js/src/moz.buildMatt A. Tobin2020-11-03
|
* Issue #1676 - Part 8: Fix up include for selfhosted.out.hMatt A. Tobin2020-11-03
|
* Issue #1676 - Part 7: Split frontend sources out of js/src/moz.buildMatt A. Tobin2020-11-03
|
* Issue #1676 - Part 6: Split ds sources out of js/src/moz.buildMatt A. Tobin2020-11-03
|
* Issue #1676 - Part 5: Split devtools sources out of js/src/moz.buildMatt A. Tobin2020-11-03
|
* Issue #1676 - Part 4: Split builtin sources out of js/src/moz.buildMatt A. Tobin2020-11-03
|
* Issue #80 - De-unify js/srcMatt A. Tobin2020-11-03
| | | | | | | Three debug sources are producing link warnings and will be solved as Issue #1676 progresses. This does not include JS Testing sources. Specifically: js/src/gdb or js/src/jsapi-tests
* Issue #1676 - Part 3: Split DEFINES out of js/src/moz.buildMatt A. Tobin2020-11-03
|
* Issue #1676 - Part 2: Split CFLAGS and CXXFLAGS directives out of ↵Matt A. Tobin2020-11-03
| | | | js/src/moz.build
* Issue #1676 - Part 1: Split MozTesting directives out of js/src/moz.buildMatt A. Tobin2020-11-03
|
* Issue #1656 - Nuke the remaining vim lines in UXPMoonchild2020-10-26
| | | | Closes #1656
* Update docs for change of repository host.Moonchild2020-10-23
| | | | Rename MCP back to MoonchildProductions.
* Update docs for change of repository host.Moonchild2020-10-23
|
* [layout] Re-order rowgroups if reflowing.Moonchild2020-10-23
| | | | This logic was missing for tfoot. See existing code in second hunk.
* [layout] Avoid negative availSize.BSizes in paginated table reflow.Moonchild2020-10-23
|
* Bump platform version for added features.Moonchild2020-10-23
|
* [netwerk] Make nsIncrementalStreamLoader's GetNumBytesRead threadsafe.Moonchild2020-10-23
| | | | | | | This prevents a potential race and simplifies the code a bit by keeping the bytes read separate instead of using mData, which is modified from another thread from OnDataAvailable. Relaxed atomics are fine for these, since they don't guard any memory.
* [DOM] When failing to create a channel and an image request, make sure to setMoonchild2020-10-22
| | | | | | | the image blocking status appropriately. This is the same status as we do for known no-data protocols and ensures we treat these two cases the same.
* [DOM Fetch] Detect broken pipes and propagate that write error to the caller.Moonchild2020-10-21
|
* [DOM Fetch] Improve stability of Fetch API.Moonchild2020-10-21
|
* Merge branch 'master' of https://github.com/MoonchildProductions/UXPMoonchild2020-10-20
|\
| * Merge pull request #1670 from athenian200/caret_colorMoonchild2020-10-20
| |\ | | | | | | Implement CSS caret-color
| | * Merge branch 'master' of https://github.com/MoonchildProductions/UXP into ↵athenian2002020-10-18
| | |\ | | |/ | |/| | | | caret_color
| | * Issue #1668 - Part 2: Visited color and auto support for caret-color property.athenian2002020-10-18
| | | | | | | | | | | | Mozilla's original implementation of this failed a couple of tests, but this seems to solve all the problems. Basically, the caret-color wasn't able to be set differently based on whether a link was visited, and the auto value implementation was incomplete. The only test we fail now is the one where you have grey text on a grey background and the caret is supposed to be visible, but I think that may have been removed from the spec. Even if it wasn't, no other browser supports it anyway.
| | * Issue #1668 - Part 1: Implement support for caret-color property.athenian2002020-10-18
| | | | | | | | | | | | | | | | | | This CSS property allows input carets (that blinking input cursor you see in text fields), to be given a custom color. This was implemented in Firefox 53, and it was such a minor feature that no one ever missed it, but I don't see any harm in implementing this. https://bugzilla.mozilla.org/show_bug.cgi?id=1063162
* | | Issue #1671 - Unprefix ::-moz-selectionMoonchild2020-10-20
|/ / | | | | | | | | | | | | | | This actually keeps both pseudo-elements for now, since the prefixed version is still used internally, but we need the unprefixed version for web compat. Note: while unprefixing a non-spec-compliant pseudo here, it's exactly in line with what other browsers do. Nobody is following the spec here and at least we'll be doing what everyone else is with our unprefixed version.
* | Issue #1643 - Follow-up: Ensure we properly clear our pointers when theMoonchild2020-10-16
| | | | | | | | Presentation of a document is destroyed.
* | Issue #1606 - Add support for multi-monitor DPI awareness v2 (W10 1706+)Moonchild2020-10-06
| |
* | [devtools] Teach devtools about overflow-wrap: anywhereMoonchild2020-10-03
| | | | | | | | Tag #1666
* | Issue #1666 - Implement overflow-wrap: anywhereMoonchild2020-10-03
| | | | | | | | | | | | | | This aligns with the current spec regarding overflow-wrap: break-word and overflow-wrap: anywhere in if it affects intrinsic sized due to considering soft-wrap opportunities or not. See CSS Text Module Level 3, Editor’s Draft, 1 October 2020, Section 5.5
* | Issue #1665 - Take overflow-wrap into account when calculating min-content ↵Moonchild2020-10-03
| | | | | | | | intrinsic size.
* | Update CONTRIBUTING.mdNew Tobin Paradigm2020-10-02
| | | | | | Revise Commit message style and add Follow-up form
* | Merge pull request #1663 from athenian200/opacity_followupMoonchild2020-10-01
|\ \ | | | | | | Remove excessive VARIANT_OPACITY statements.
| * | Issue #1647 - Followup: Remove excessive VARIANT_OPACITY statements.athenian2002020-09-30
|/ / | | | | | | | | | | | | | | I got very anxious about making sure I included VARIANT_OPACITY in all the places VARIANT_NUMBER was included to make sure it couldn't possibly break unexpectedly, and that led to me accidentally breaking a mechanism that prevented percentages from serializing as numbers in other parts of the code. It was a total accident, and these additions were unnecessary. Basically, the situation is that there was one part of the code where it determines what's allowed for the flex statement (and possibly other statements) by checking whether it got stored as a "number", and basically only disallows percentages if it attempted to store/serialize them as percentages. However, it only got to that part of the code because I accidentally allowed VARIANT_OPACITY as a valid way for certain tokens to parse where it wasn't necessary. If it tries to parse it that way under very specific circumstances... percentages will be marked valid and fed through the system as numbers rather than being rejected and not serialized at all, because the check to disallow percentages there relied on them being stored as percentages. It's a really weird thing to have a problem with in a lot of ways, because if percentages aren't allowed in a field, you would think people wouldn't try to use them there, much less depend on the broken behavior that results from them not parsing as a related value.
* | Issue #1643 - Follow-up: Make sure things aren't changed while iterating.Moonchild2020-09-30
| | | | | | | | This fixes some crashing scenarios.
* | Issue #1643 - Follow up: Add a null check for mOwner in ↵Matt A. Tobin2020-09-29
| | | | | | | | | | | | | | ResizeObserverNotificationHelper::Unregister A race condition seemed to exist between tab destruction and un-registering a ResizeObserver resulting in a null deref crash. The original reporter in Forum Topic 25311 experienced this on msn.com so that was the functional test reference.
* | Merge pull request #1660 from g4jc/1656Moonchild2020-09-27
|\ \ | | | | | | Issue #1656 - Fix broken comment from Part 1
| * | Issue #1656 - Fix broken comment from Part 1Gaming4JC2020-09-26
|/ / | | | | | | Removing the vim line unintentionally broke the comment leading to build failure, this restores the comment.
generated by cgit v1.2.3 (git 2.26.2) at 2024-11-15 12:07:43 +0000