One of the things I've always liked about javadoc is that it has the feel of a
static web page. Of course, it was completely static initially. As time has gone
on it's become more interactive, yet the static feeling is still there. I think
this is a big advantage, because it gives me (the user)
Prefer #3
Works on Mac with Brave and Safari with symptom Mauricio mentioned.
The blue border on search is and close icon is overlapped with Brave, but
that’s nit-picking.
Cheers,
Henry
> On Oct 9, 2019, at 10:29 AM, Hannes Wallnöfer
> wrote:
>
> The javadoc team is considering changes
Hi Hannes,
On 10/10/2019 11:39, Hannes Wallnöfer wrote:
However, the whole focus grabbing is certainly a potential source of
confusion/problems.
Yes, I think it could be the source of confusion.
In Firefox, I have the "Search for text when you start typing" option
selected (it's in the Browsi
Proposal #3 seems a good compromise to me. Thanks for those proposals
Martin
Thanks for the hint, Sergey.
(Removing jdk-dev but leaving javadoc-dev recipient as this is a more technical
issue.)
The changes I have done should have no effect for a11y tools like screen
readers. We do have an invisible „Skip navigation links“ link though that
should allow skipping over nav
Thanks for the feedback, Maurizio.
> Am 09.10.2019 um 22:27 schrieb Maurizio Cimadamore
> :
>
> #3 is the one I prefer; it is subtle (compared to #2), offer some benefits
> (as Alex said) in terms of screen estate, and, indirectly put the search bar
> front and center, as it should be.
>
> I
Thanks for the feedback, Alex.
> Am 09.10.2019 um 20:33 schrieb Alex Buckley :
>
> On 10/9/2019 10:29 AM, Hannes Wallnöfer wrote:
>
> People should remember that the search bar often contains overview
> information of its own -- not on the top-level javadoc page, but on module
> and class page
