Props allocated with dispex_get_dprop_ref or dispex_get_dynid are purely
internal to our implementation and must not be enumerated.
Note that in case of window, the props themselves become enumerable, but the
dynamic props must still be hidden, since it's the custom prop that refers
to it that must be enumerated (i.e. the DISPID must match with the custom
prop, not the underlying dynamic prop backing it, which would violate the
former DISPID obtained for the respective name).
Signed-off-by: Gabriel Ivăncescu <gabrielopcode@gmail.com>
If properties were added during enumeration, for example on the prototype,
they are actually visited in mshtml scripts in any mode.
Signed-off-by: Gabriel Ivăncescu <gabrielopcode@gmail.com>
It should fix the errors around line 1370 in conhost/tests/tty.c, but
it doesn't fix other errors around line 1530 and 1550 which are
completly unrelated to this change. So failures to be expected on the
latter.
Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=52648
Signed-off-by: Eric Pouech <eric.pouech@gmail.com>
Partly reverting 99eb63bd7a
(it's still needed on Dwarf for blocks with multiple
non-contiguous address ranges).
Signed-off-by: Eric Pouech <eric.pouech@gmail.com>
Current code skips a character and goes on to run is_namechar the next
instead of the current character ultimately always running a null
string on is_namechar and therefore always returning error on
multi-character strings
Signed-off-by: David Kahurani <k.kahurani@gmail.com>
XWayland tablet devices have the Wayland seat ID appended to the end of
them, preceded by a colon. This prevents match_token from properly
detecting XWayland devices and causes Wintab32 to fail to initialize.
This change allows a matched token to end in a colon, and thus allows
XWayland tablet devices to be detected correctly.
Signed-off-by: John Chadwick <john@jchw.io>
The only way to actually set these properties is via the ICommandProperties interface
found on ICommandText(eg rowset->caller).
Signed-off-by: Alistair Leslie-Hughes <leslie_alistair@hotmail.com>
On ARM and ARM64, each SEH opcode is supposed to map to exactly one
instruction; the operation of writing x29+x30 with a stack offset
with writeback is called ".seh_save_fplr_x".
Using the right opcode would fix inconsistent unwinding if we would
unwind from near the end of the prologue (which is implausible here).
However, clang/LLVM might also get checking for mismatches between
SEH opcodes and the prolog/epilog ranges
(https://reviews.llvm.org/D131394), mainly to guard against
inconsistencies in the unwind info generated by the compiler, but
that would trigger on this handwritten function too.
Prints 'int a[10]' (instead of 'int[10] a').
Ditto for variables/fields of type function pointer.
And for pure type printing, no longer prints --none-- for
arrays and function pointers.
Signed-off-by: Eric Pouech <eric.pouech@gmail.com>
