mstr2
mstr2
> I can confirm that this change fixes a Problem for more users. Actually, i have a built with exactly the same change. So if this doesn't break anything, it...
> A general question: what would be an example of when `focused != focusVisible` (and `!= focusWithin`) ? > > Shouldn't the `focused` be a sort of "primary" property, and...
Just to complete the picture, I also want to explain why I am strongly against making `focusVisible` writable. The (much older) `focused` property is an example of bad API design:...
> It's one of the falsehoods programmers should be aware of. > > But regardless of how they interact with the UI, the focus indicator should always indicate the focus...
> Getting back to the API, are you ok with dropping the boolean `visible` argument and documenting the expectation of the key event? Yes, I think that's okay.
> > Can this class be sealed? > > Theoretically, yes, but what problem would that solve? > > I can understand when sealing would make the platform more secure,...
Just a linguistic observation: the defining feature of a watermark is that it is always present on the marked object (for example in postage stamps, currency or a 'digital watermark')....
> What is the benefit of this change? It enforces a system invariant at compile-time instead of run-time. > Also, this change is breaking. One can currently create a Node:...