[webkit-dev] Is the New XMLParser dead?
abarth at webkit.org
Mon Aug 27 15:48:33 PDT 2012
On Mon, Aug 27, 2012 at 3:06 PM, Maciej Stachowiak <mjs at apple.com> wrote:
> On Aug 27, 2012, at 2:45 PM, Eric Seidel <eric at webkit.org> wrote:
>> Checking back in:
>> Curious if this effort is still underway. Adam and I would like to
>> delete the New XML Parser if it's not needed in order to simplify the
>> HTML 5 Parser again. :)
> We do tentatively plan to get back to it (the original implementor is currently working full-time at Apple on the WebKit team).
As far as I can tell, no one has worked on the NEWXML code in over a
year, the implementation doesn't work, and the code is disabled by all
ports. It seems like we should remove it from trunk. We can retore
it if/when someone is interested in working on it again.
> As far as simplifying the HTML5 parser - isn't most of the foundational work that touches the HTML5 parser also required for WebVTT, as mentioned by me in the email you quote below? Is there a big simplicity win to be had without breaking WebVTT? If so, we can think about whether removing the scaffolding and reconstructing it when needed is worthwhile.
This is a separate issue.
>> On Thu, Mar 15, 2012 at 1:58 PM, Maciej Stachowiak <mjs at apple.com> wrote:
>>> On Mar 15, 2012, at 1:29 PM, Eric Seidel wrote:
>>>> It seems the "New XML Parser" hasn't been touched in about 8 months:
>>>> Are there any plans to continue work on such, or can it be removed?
>>>> The refactoring which was done to support it seems to mostly just
>>>> confuse the HTML 5 Parser code... :(
>>>> (I went looking for how something was implemented in the HTML5
>>>> parser... and it took me a long time to find it this afternoon).
>>> Yes, we plan to get more active on this effort again within a few months.
>>> Note that some of the refactoring was able to benefit the WebVTT parser, so we need some generic parser abstractions in any case.
> webkit-dev mailing list
> webkit-dev at lists.webkit.org
More information about the webkit-dev