https://bugzilla.wikimedia.org/show_bug.cgi?id=16165

--- Comment #48 from Matthew Flaschen <[email protected]> ---
> It is, however, a problem with the change - if the functionality is hidden, 
> and
> if there is a real need for it, then that is a problem.

It's not hidden at all.  The mouseover behavior indicates that it
behaves like a link.  Some people won't get that cue, but a lot will.

> Given that this is a somewhat heavy-handed js workaround, I would hope that 
> there is indeed a real
> need for it if it is to be added to core.

There is a need, and that's why people are using it on en wiki, and why
someone else asked for it to be added to core.

>> No one has told me it confused them (or someone else) about other buttons.  
> 
> In many cases this may already be expected behaviour, as modern browsers
> (chrome and opera, at least) support such functionality already, but as most
> people indeed do not know about this at all, of course it will not confuse
> them.

I'm actually not sure if that's true.  Shift-click does not work for me
in Firefox or Chrome.

> If some people want this and it's not supposed to affect others, why does it
> belong in core?

It is valuable to a large enough group already to justify core, and the
fact that it's *exposed* on mouseover (very unlike these possible Shift
solutions) will make it useful to others (even without docs, but of
course we will write those too).

As mentioned, it's also way more flexible than any "just open in a new
window" built-in feature.

-- 
You are receiving this mail because:
You are watching all bug changes.
_______________________________________________
Wikibugs-l mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l

Reply via email to