Chad H. <> changed:

           What    |Removed                     |Added
                 CC|                            |
           Severity|enhancement                 |minor

--- Comment #6 from Chad H. <> 2010-08-26 19:06:22 UTC 
Not an enhancement, this is a bug. I've disagreed with this choice since the
beginning (I complained somewhere...). 

(In reply to comment #3)
> > the visual context and space constraints are unique to Vector, and
> > should not be assumed to be the same as other skins.
> That could be argued for all skins. "My skin is so special it needs an 
> specific
> message".

This. And no, skins aren't so special. Skins are designed to present a
different visual look to a page. The elements of the page should retain their
familiar names across all skins.

> I don't see such need for at least the provided examples. Of course, the
> ability of giving eg. a large name for vector, is neat, but that will bite us
> later when the two sets of tabs gets desynchronized.

They can and they will. And we will inevitably get complaints that "When I
changed nstab-whatever it didn't work in Vector"

> We could get the best of both worlds by doing everywhere
> wfEmptyMsg('vector-namespace-main') ? wfMsg( 'nstab-main' ) :
> wfMsg('vector-namespace-main') but that looks ugly.

Ugh. You *could* do that in Vector. Preferably we should just chunk the
redundant messages entirely.

Configure bugmail:
------- You are receiving this mail because: -------
You are on the CC list for the bug.

Wikibugs-l mailing list

Reply via email to