| Commit message (Collapse) | Author | Age |
|
|
|
| |
Based-on: m-c 1479659/2
|
|
|
|
| |
Based-on: m-c 1479659/{1,12}
|
|
|
|
|
|
| |
which returns bool
Based-on: m-c 1479659/0
|
|
|
|
|
|
| |
the switch ParseNode
Based-on: m-c 1477157
|
|
|
|
|
|
| |
property access name
Based-on: m-c 1378808/2
|
|
|
|
|
|
| |
Also change PNK_GENEXP (not supported by upstream) to a PN_BINARY node
Based-on: m-c 1378808/1
|
|
|
|
|
|
|
|
| |
Examples:
export const [name1, name2] = [1, 2];
export var {...name} = get;
Based-on: m-c 1446811, m-c 1462286
|
|
|
|
|
|
|
|
|
| |
spec change
Fix regression from difference between Interpreter (old) and ElemOpEmitter (new). We don't have
any Ion/IC support for these ops.
Based-on: m-c 1472211
|
|\
| |
| |
| |
| |
| | |
(#2188) from jobbautista9/UXP:freebsd-xz into master
Reviewed-on: https://repo.palemoon.org/MoonchildProductions/UXP/pulls/2188
|
|/
|
|
| |
Currently it defaults to bzip2, which has been obsolete for us.
|
|\
| |
| |
| |
| |
| | |
(#2187) from jobbautista9/UXP:62-jsprincipals-debug-fix into master
Reviewed-on: https://repo.palemoon.org/MoonchildProductions/UXP/pulls/2187
|
|/
|
|
| |
A method marked with dllimport shouldn't be defined.
|
|\
| |
| |
| |
| |
| | |
MiB.' (#2185) from jobbautista9/UXP:2184-mozjemalloc-12 into master
Reviewed-on: https://repo.palemoon.org/MoonchildProductions/UXP/pulls/2185
|
|/
|
|
|
| |
We don't need the reduced memory overhead as we are not using e10s. This
should speed up JS by a point according to Speedometer 2.1.
|
|\
| |
| |
| |
| |
| | |
jobbautista9/UXP:2181-auxv into master
Reviewed-on: https://repo.palemoon.org/MoonchildProductions/UXP/pulls/2183
|
|/
|
|
| |
This should fix getauxval being undefined when building highway on Linux ARM64.
|
|\
| |
| |
| |
| |
| | |
Big Sur 11.0 SDK.' (#2182) from dbsoft/UXP:drawintitlebar into master
Reviewed-on: https://repo.palemoon.org/MoonchildProductions/UXP/pulls/2182
|
|/
|
|
|
|
|
|
|
| |
11.0 SDK.
On Intel we build with the 10.12 SDK so this problem is avoided.
Also Pale Moon no longer supports drawing in the titlebar in the front end.
However Basilisk does and built for ARM the tabs were cut off by the native titlebar.
This uses the new APIs introduced in SDK 10.10 and 11.0 to draw in the titlebar.
|
| |
|
| |
|
|\
| |
| |
| |
| |
| | |
martok/UXP-contrib:mr/bce-split2 into master
Reviewed-on: https://repo.palemoon.org/MoonchildProductions/UXP/pulls/2179
|
| |
| |
| |
| | |
Based-on: m-c 1456006/{0,1}
|
| |
| |
| |
| |
| |
| | |
ForOfLoopControl.{cpp.h}
Based-on: m-c 1460489/5
|
| |
| |
| |
| |
| |
| | |
BytecodeControlStructures.{cpp.h}
Based-on: m-c 1460489/3
|
| |
| |
| |
| | |
Based-on: m-c 1351107/17, m-c 1460489/2
|
|\ \
| | |
| | |
| | |
| | |
| | | |
tvall43/UXP:master into master
Reviewed-on: https://repo.palemoon.org/MoonchildProductions/UXP/pulls/2177
|
| |/ |
|
|\ \
| | |
| | |
| | |
| | |
| | | |
ICU as shared lib in Windows.' (#2164) from jobbautista9/UXP:62-shared-mozjs into master
Reviewed-on: https://repo.palemoon.org/MoonchildProductions/UXP/pulls/2164
|
| | |
| | |
| | |
| | |
| | |
| | | |
Shared JS is confirmed working fine in Windows after a week of testing.
Non-Windows will have to wait unfortunately. The JS_SHARED_LIBRARY option is
kept for easy testing on those unsupported platforms.
|
| | |
| | |
| | |
| | | |
they're too spammy.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The trace in Spidermonkey's old-configure is causing the MOZ_CONFIG_ICU function
to be called twice, which is not desirable as it can cause the MOZ_SHARED_ICU
check in build/autoconf/icu.m4 to fail and build an ICU data file even if we're
building ICU as a shared library.
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
file into packaging, fold it into the ICU shared library, and always build ICU shared."
This reverts commit 0c63f5a27346875dd04c8bb41eced35203d20567.
Building shared ICU is currently broken in non-Windows, so we need the option for now.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
packaging, fold it into the ICU shared library, and always build ICU shared.
This removes two variables in the build system: MOZ_ICU_DATA_ARCHIVE and
MOZ_SHARED_ICU.
Per discussion in PR #2164, it's now preferred to fold the ICU data into the new
shared library.
This effectively means --enable-shared-icu is no longer a thing. UXP apps must
update their packaging manifest to avoid breakage.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
shared.
It seems that if we're going to enable JS_SHARED_LIBRARY, we need ICU to be a
shared library too in order to prevent code duplication in mozjs.dll bloating
it to a whopping 21 MB.
This unfortunately means we have to fold icudata back to icu itself. But since
icudata is still separated from libxul (which is what really matters for #1451),
I think this is a fair compromise.
Building ICU as shared is offered as an option via --enable-shared-icu. But
technically you really need --enable-shared-icu if you're going to use
--enable-shared-js. Unfortunately I can't make configure exit with an error if
MOZ_SHARED_ICU is not defined when JS_SHARED_LIBRARY is enabled, because options
are controlled by different configure scripts (icu is based on bash, while js is
based on python), and I have no idea how to pass MOZ_SHARED_ICU to js's
moz.configure.
Tag #62
|
| | |
| | |
| | |
| | |
| | | |
This is the one I don't understand how it fixed the bustage. Why is it needed
to remove JS_PUBLIC_API..? It would seem counter-intuitive, but it wasn't...
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
The unsafeSet method is based on Jon Coppeard's part 2 patch for Mozilla bug
1306008. This is needed because of the use of unsafeSet in rekey() of
MovableCellHasher<JS::Heap<T>>
|
| | |
| | |
| | |
| | | |
fix link bustage related to ICU when doing shared lib
|
|\ \ \
| |_|/
|/| |
| | |
| | |
| | | |
`display:contents` nodes' (#2178) from 2176 into master
Reviewed-on: https://repo.palemoon.org/MoonchildProductions/UXP/pulls/2178
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
display:contents nodes with pseudo-elements.
We need to use StyleChildrenIterator which iterates over them, instead.
This is a bit of a hack but we can't always have our cake.
We need to be a bit careful though, since ::before and ::after are owned
by their own frame, and thus could be unbound from the tree or even dead
after removing the frame.
This basically ports bugs 1435566 and 1438467
|
|\ \ \
| |/ /
|/| |
| | |
| | |
| | | |
`::slotted()` or `:host` arguments' (#2174) from FranklinDM/UXP-contrib:work_css-host-slotted-retain-event-states into master
Reviewed-on: https://repo.palemoon.org/MoonchildProductions/UXP/pulls/2174
|
| | |
| | |
| | |
| | |
| | |
| | | |
:host arguments
This should fix issues with selectors like :host(:hover) that continue to be matched although the cursor is no longer hovering over those elements.
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
key combination doesn't input any character
Currently, we dispatch keypress event when Enter is pressed without
modifiers or only with the Shift key (line break).
However, other browsers dispatch keypress events for Ctrl + Enter also
even if it doesn't cause any text input.
So, we should fire keypress events for Ctrl + Enter, even in strict
keypress dispatching mode. Note that with other modifiers, it depends on
the browser and/or platform and we can't dispatch the event for
consistent behavior.
This means web developers shouldn't rely one keypress events to catch
Alt + Enter, Meta + Enter and two or more modifiers + Enter.
Based on BZ 1438133
Resolves #2161
|
|\ \ |
|
| | |
| | |
| | |
| | | |
This fixes a potential crash caused if restyleElement is null.
|
| | |
| | |
| | |
| | | |
attribute changes
|
| | |
| | |
| | |
| | | |
slottable
|
| | |
| | |
| | |
| | | |
instead of the slottable when matching ::slotted()
|
| | | |
|