Re: Redirects for prefixed features

There's a benefit in having these as -moz-transform, -webkit-transform,
etc, with redirects in the wiki content. It'll redirect as wanted, but will
give context to the user with "redirected from -webkit-transform". It's
also possible to not redirect, but to educate users on those pages, for
instance: "-moz-transform is a Mozilla specific... blah blah, here's a link
to the content you are looking for"

Things like this are usually handled on Wikimedia projects with a bot.
There's a special permission that allows bot edits to be marked as minor by
default, which means it can be ignored in Recent Changes and watchlists.

That said, it likely is a relatively minor apache rewrite change, so that
would indeed be quicker.



On Mon, Mar 25, 2013 at 5:15 PM, Lea Verou <lea@w3.org> wrote:

> Hi all,
>
> I was thinking that some inexperienced authors might search for things
> like -webkit-transform or -moz-transform instead of transform, because
> that’s what they saw in someone else’s code and assumed it was the property
> name. This is especially likely if they saw code from people who didn’t
> include an unprefixed version along with their prefixed declarations.
>
> MDN has redirects for these. I’m not sure if it’s manual or automatic, but
> it looks manual.
>
> I think it would be a good idea to set up redirects for these features as
> well. If we don’t intend to ever have separate documentation for prefixed
> features (are we going to document proprietary features?), it could be
> automatic, with mod_rewrite rules. I can help with these.
>
> Thoughts?
>
>  Lea Verou
> W3C developer relations
> http://w3.org/people/all#lea ✿ http://lea.verou.me ✿ @leaverou
>
>
>
>
>
>
>