[prev in list] [next in list] [prev in thread] [next in thread] 

List:       wikitech-l
Subject:    Re: [Wikitech-l] HTML5 and non valid attributes/elements of previous versions (bug 40329)
From:       Derk-Jan Hartman <d.j.hartman+wmf_ml () gmail ! com>
Date:       2012-09-29 14:13:59
Message-ID: BF51C9C5-81E1-434A-BC02-4057940146D8 () gmail ! com
[Download RAW message or body]

I'm on vacation, but it seems discussion is getting a bit out of control here: \
https://bugzilla.wikimedia.org/show_bug.cgi?id=40329 If someone can bring back some \
sensibility .....

BTW this has been 'broken' for weeks now, we should take some actual action, or just \
accept the status quo.

DJ

On 27 sep. 2012, at 23:07, Daniel Friesen <daniel@nadir-seen-fire.com> wrote:

> A bit of a side topic. But could someone point out some urls where the \
> deprecated/removed align attribute is used along with block elements that are \
> supposed to be centered too. 
> I've seen a lot of WikiText. But frankly, I have never seen any article or template \
> that even tried to use align to center non-inline content (besides {| \
> align=center). 
> -- 
> ~Daniel Friesen (Dantman, Nadir-Seen-Fire) [http://daniel.friesen.name]
> 
> On Wed, 19 Sep 2012 09:23:37 -0700, Derk-Jan Hartman <d.j.hartman+wmf_ml@gmail.com> \
> wrote: 
> > I would like to open some discussion about
> > https://bugzilla.wikimedia.org/show_bug.cgi?id=40329
> > This bug is about the fact that we currently do a 'partial' transform of
> > the HTML5-invalid attribute 'align'.
> > 
> > We all agree that this is bad, what we need to figure out is what to do
> > next:
> > 
> > 1: Disable the transform and output the align attribute even though it's
> > not valid HTML5. Solve validness later.
> > 2: Remove the attribute from HTML5 and 'break' the content. Fix by users
> > (or bot).
> > 3: Disable HTML5, correct the content of the wiki's (possibly with a bot)
> > and remove the attribute in HTML5 mode, reenable HTML5.
> > 4: Fix the transform (not that easy)
> > 
> > My personal preference is with 1, since this is causing trouble now and
> > with 1 we solve immediate problems, we just add to the lack of valid HTML5
> > output that we already have. In my opinion 2 would be too disruptive and 3
> > would take too long.
> > 
> > Danny is of the opinion that we should never transform at the parser side
> > and that we should fix the content instead (2 or 3).
> > 
> > So, how best to fix the issue/what should be our strategy with regard to
> > content that is not HTML 5 valid in general ?
> > <Discuss>
> > 
> > DJ
> 
> 
> _______________________________________________
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l


_______________________________________________
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l


[prev in list] [next in list] [prev in thread] [next in thread]