Currently, the color scheme of a system-decorated stage is as follows:
* On Windows, the title bar is always light (even if the OS color scheme is
dark).
* On macOS and Linux, the title bar is light or dark depending on the OS color
scheme.
The expected behavior is that the title bar matches the
Yeah that would definitely improve the situation when it comes to
repetitiveness. Would I need to define such custom media queries per
stylesheet or can they apply globally?
On 12/07/2025 20:24, Michael Strauß wrote:
Maybe @custom-media queries can get you part of the way there:
https://www.w3
> Implementation of [viewport characteristics media
> features](https://www.w3.org/TR/mediaqueries-5/#mf-viewport-characteristics):
> * `width`
> * `height`
> * `aspect-ratio`: width / height
> * `orientation`: `portrait`, `landscape`
> * `display-mode`: `fullscreen`, `standalone` (note: `browser`
Maybe @custom-media queries can get you part of the way there:
https://www.w3.org/TR/mediaqueries-5/#custom-mq
So instead of repeating a media query multiple times, you can define a
custom media query like this:
@custom-media --sm (width >= 40);
And use it with the regular syntax:
@media
Assuming this would be available, I would implement custom css
breakpoints to refer to common layout changes for our application. This
would prevent a lot of repetition. For example, something similar to the
tailwindcss breakpoints:
I could also use it to define more advanced breakpoint condi
In general, I'm skeptical about inventing non-standard CSS features.
What would be the use case for custom properties in the way that you describe?
On Sat, Jul 12, 2025 at 6:03 PM Christopher Schnick wrote:
>
> That is very exciting.
>
> Would it be possible to create custom boolean properties t
That is very exciting.
Would it be possible to create custom boolean properties that one can
then use for media queries? For example, having a ObservableMapObservableBooleanValue> in the new scene preferences to define custom
features that can then be matched in the stylesheet.
On 12/07/2025
On Fri, 11 Jul 2025 15:11:27 GMT, Kevin Rushforth wrote:
>> This PR adds an introductory section to the JavaFX API docs similar to that
>> of the JDK docs.
>>
>> Compare the [JavaFX 24 API
>> docs](https://download.java.net/java/GA/javafx24/docs/api/index.html) with
>> the [JDK 24 API
>> doc
Hi,
We recently noticed a problem: For fonts with localized names,
Font.font(String) can only find the font based on the localized name in the
current locale.
For example, the Chinese version of Windows comes with a font called
"YouYuan", and its Chinese name is "幼圆".
When the system language is
On Thu, 10 Jul 2025 19:43:15 GMT, Andy Goryachev wrote:
>> I thought about this as well. No strong opinion from my side.
>
> there should be no noise: it's more of a question of instructing the
> developer why their test failed. if there is no message, the NPE will happen
> in the context of t
> Currently, the VirtualFlowTestUtils used ONLY for tests has many utility
> methods to get and do something with the VirtualFlow of Virtualized Controls.
>
> It has one flaw: It may creates a temporary Stage with the StageLoader, when
> the Control was never inside a Scene (and Stage) yet. This
On Fri, 11 Jul 2025 16:30:14 GMT, Martin Fox wrote:
> > Does `resolveFocusDelegate` do what you need?
>
> Currently we turn on input method processing at the platform level if and
> only if there's any control in the focus chain that is set up to receive
> input method events and respond to in
12 matches
Mail list logo
