On Sat, 25 May 2024 13:50:56 GMT, Kevin Rushforth wrote:
>> The code looks good. I didn't test it, but I'm fine with integrating.
>
>> Also some clarification on the contributing rules: "all Reviewers who have
>> requested the chance to review have done so" -- does the indication at the
>> top
> Improves performance of selector matching in the CSS subsystem. This is done
> by using custom set implementation which are highly optimized for the most
> common cases where the number of selectors is small (most commonly 1 or 2).
> It also should be more memory efficient for medium sized and
> Improves performance of selector matching in the CSS subsystem. This is done
> by using custom set implementation which are highly optimized for the most
> common cases where the number of selectors is small (most commonly 1 or 2).
> It also should be more memory efficient for medium sized and
> Improves performance of selector matching in the CSS subsystem. This is done
> by using custom set implementation which are highly optimized for the most
> common cases where the number of selectors is small (most commonly 1 or 2).
> It also should be more memory efficient for medium sized and
On Tue, 21 May 2024 14:25:51 GMT, Michael Strauß wrote:
> This PR fixes a bug
> ([JDK-8289115](https://bugs.openjdk.org/browse/JDK-8289115)) that was
> introduced with #394, which changed the following line in the
> `NotifyTouchInput` function (ViewContainer.cpp):
>
> - const bool isDirect =
> This PR fixes the problem that maximizing/fullscreen a `Stage` or `Dialog` is
> broken when `sizeToScene()` was called before or after.
>
> The approach here is to ignore the `sizeToScene()` request when the `Stage`
> is maximized or set to fullscreen.
> Otherwise the Window Manager of the OS
> This PR fixes the problem that maximizing/fullscreen a `Stage` or `Dialog` is
> broken when `sizeToScene()` was called before or after.
>
> The approach here is to ignore the `sizeToScene()` request when the `Stage`
> is maximized or set to fullscreen.
> Otherwise the Window Manager of the OS
On Sun, 26 May 2024 08:08:26 GMT, Michael Strauß wrote:
>> Implementation of [CSS
>> Transitions](https://gist.github.com/mstr2/c72f8c9faa87de14926978f517a6018a).
>>
>> ### Future enhancements
>> CSS transitions requires all participating objects to implement the
>> `Interpolatable` interface.
On Mon, 27 May 2024 09:30:18 GMT, Thiago Milczarek Sayao
wrote:
>> Wayland implementation will require EGL.
>>
>> EGL works with Xorg as well. The idea is to be EGL first and if it fails,
>> fallback to GLX. A force flag `prism.es2.forceGLX=true` is available.
>>
>>
>> See:
>> [Switching th
> Wayland implementation will require EGL.
>
> EGL works with Xorg as well. The idea is to be EGL first and if it fails,
> fallback to GLX. A force flag `prism.es2.forceGLX=true` is available.
>
>
> See:
> [Switching the Linux graphics stack from GLX to
> EGL](https://mozillagfx.wordpress.com
> This replaces obsolete XIM and uses gtk api for IME.
> Gtk uses [ibus](https://github.com/ibus/ibus)
>
> Gtk3+ uses relative positioning (as Wayland does), so I've added a Relative
> positioning on `InputMethodRequest`.
>
> [Screencast from 17-09-2023
> 21:59:04.webm](https://github.com/openj
On Thu, 23 May 2024 10:53:36 GMT, Thiago Milczarek Sayao
wrote:
>> This fixes two bugs appointed on the JBS issue:
>>
>> 1) Sometimes window was moving to the top left corner - seems to be a bug
>> somewhere in `gdk_window_get_origin` when used before map (a X concept when
>> the window appea
On Fri, 24 May 2024 18:18:22 GMT, Hima Bindu Meda wrote:
> Updated libxml to v2.12.7. Sanity testing looks fine. No issue seen
Tests are green here as well.
-
Marked as reviewed by sykora (Author).
PR Review: https://git.openjdk.org/jfx/pull/1464#pullrequestreview-2080216007
13 matches
Mail list logo
