On Sun, Jan 21, 2018 at 10:07 AM, Andrea Aime <andrea.a...@geo-solutions.it>
wrote:
> On Mon, Jan 15, 2018 at 7:06 PM, Torben Barsballe <
> tbarsba...@boundlessgeo.com> wrote:
>
>> UI improvements are always nice, and this seems like a particularly
>> useful one.
>>
>> The style differences relative to native drop-downs are a bit annoying,
>> but seem fine. One possible alternate workaround for that would be to style
>> the regular drop-downs so that they are the same between browsers. That
>> should be as simple as adding a bit of CSS (Although most of the methods I
>> could find for this used a background image to replace the select, so this
>> workaround seems a bit finicky).
>>
>
> Indeed... I looked around but could not find an approach that would scale
> well along the the base system font size changes... (there are some
> bootstrap based examples that might work, but we don't use bootstrap in
> GeoServer so...).
>
>
Ah, forgot about scaling; yeah that would make things rather more difficult.
> Can you think of any other case in the UI that would benefit from having
> the select2 list?
>
Hmm... List of requests on the Demo requests page. Likewise, list of WPS
processes on the WPS request builder demo. Preview format on Layer Preview
page.
You could maybe change the CRS fields on the Layer / Layer group edit page
to use it, but that seems like a bit more work.
>
>> I think we should probably avoid replacing all drop-downs with the
>> select2 one just for style reasons, seems like it could be a bit
>> annoying/unnecessary where there are only a few options.
>>
>
> Yeah, I was wondering myself. Personally I'd prefer visual consistency but
> I have no strong opinion on this one, happy to leave it as is.
>
>
>> One thing I did notice is that the select2 drop-down doesn't support
>> keyboard navigation (tab + arrow keys), unlike a regular select. That seems
>> like another good reason to only use it where necessary.
>>
>
> That is indeed annoying (although not sure how keyboard friendly the UI is
> to start with).
>
>From what I have seen / tried, navigating by keyboard is a bit finicky, but
still technically doable.
> Hmmm... seems like it may be fixable, I'll have a look into it:
> https://github.com/select2/select2/issues/3472
>
> If a viable fix comes out of that, then I wouldn't see an issue with
replacing all select boxes with the select2 one. As-is, I think the
accessibility improvement of the regular select boxes outweighs the style
consistency.
Cheers,
Torben
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
