Hi All,
Thanks for your valuable inputs regarding Microdata implementation.
I have uploaded the patch for basic implementation of document.getItems()
DOM API.
Bug id: https://bugs.webkit.org/show_bug.cgi?id=68610
Could someone please review the patch, and let me know the review comments.
Thanks
On Sun, Sep 25, 2011 at 9:12 AM, Ryosuke Niwa wrote:
> On Sun, Sep 25, 2011 at 2:30 AM, Adam Barth wrote:
>> Yeah, I'm not sure where we should draw the line, but this case seems
>> pretty clearly in the "unmaintained" camp, as was the old Android
>> port. Maybe a good rule of thumb is something
On Sep 25, 2011, at 12:20 AM, James Robinson wrote:
> The TIMER based support for RAF is very new (only a few weeks old) and still
> has several major bugs. I'd suggest letting it bake for a bit before
> considering turning it on for all ports.
Got it.
> Fundamentally I don't think this featur
Fair enough. Rough consensus among reviewers sound good to me.
- Ryosuke
On Sep 25, 2011 11:16 AM, "Geoffrey Garen" wrote:
>> Following this pattern, giving a warning then waiting for some period of
time might be sufficient. e.g.
>> Warn the port (probably on webkit-dev)
>> Wait for six months
>>
I have smacked into a problem which appears to have it's root within Webkit.
However, I'm well outside of my familiar territory and am seeking some help
to further understand the issue and formulate a useful bug report, if
appropriate.
Here's the background:
1. I have a web page with a TinyMCE e
> Following this pattern, giving a warning then waiting for some period of time
> might be sufficient. e.g.
> Warn the port (probably on webkit-dev)
> Wait for six months
> If there's no activity in step 2 to counter the argument, then remove the
> port.
You might think this leniency is friendly
I think removing Haiku port is a good thing given they don't even have build
bots or EWS bots. We can't even tell if they compile or not.
On Sun, Sep 25, 2011 at 2:30 AM, Adam Barth wrote:
>
> Yeah, I'm not sure where we should draw the line, but this case seems
> pretty clearly in the "unmaintai
> As part of our effort to reduce complexity in WebKit, I believe it is
> now time to remove the Haiku port.
+1
Geoff
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
On Sun, Sep 25, 2011 at 2:16 AM, Xan Lopez wrote:
> On Sun, Sep 25, 2011 at 9:34 AM, Adam Barth wrote:
>> As part of our effort to reduce complexity in WebKit, I believe it is
>> now time to remove the Haiku port.
>
> Perhaps it would make sense to have a small set of simple rules
> written down
On Sun, Sep 25, 2011 at 9:34 AM, Adam Barth wrote:
> As part of our effort to reduce complexity in WebKit, I believe it is
> now time to remove the Haiku port.
Perhaps it would make sense to have a small set of simple rules
written down somewhere that would justify the WebKit developers in
removi
On April 9, 2010, I wrote an email to webkit-dev asking if it was time
to remove the Haiku port:
http://old.nabble.com/Archiving-the-Haiku-port--(was-WebKit2-and-all-that-jazz)-td28197730.html
At the time, the port appeared inactive. Stephan Assmus and Maxime
Simon wrote that they planned to con
On Sat, Sep 24, 2011 at 11:29 PM, Adam Barth wrote:
> On Sat, Sep 24, 2011 at 11:21 PM, Adam Barth wrote:
> > On Thu, Sep 15, 2011 at 11:06 AM, Adam Barth wrote:
> >> On Wed, Sep 14, 2011 at 11:06 PM, Darin Fisher
> wrote:
> >>> What about ENABLE(REQUEST_ANIMATION_FRAME)?
> >>
> >> That might
12 matches
Mail list logo
