bmozumder at gmail.com
Fri Mar 27 14:45:55 PDT 2015
Thank you for the feedback.
I haven’t heard a response from them and haven’t asked any other vendor directly.. I started with Webkit first as that’s what I’m most familiar with, and our fashion audience is mostly Mac/iOS Safari anyways. (then Chrome, then IE, then finally a bit of Firefox)
I’ll check with the other vendors, but right now is it a definite no or more of skepticism/not enough info? (which is fine, as I expect this process to take years to go through, figure out specs, security holes, prototypes, implementations, etc..)
Some of the comments and feedback web developers put out include that view as well, that declarative dynamic reloads should have been a basic part of HTML.
> On Mar 27, 2015, at 2:02 PM, Benjamin Poulain <benjamin at webkit.org> wrote:
> Did any vendor actually respond positively to the whatwg proposal?
> On 3/27/15 12:49 AM, Bobby Mozumder wrote:
>> I submitted a proposal to W3C & WHATWG to enhance HTML to support
>> And here’s a document on Github that’s clearer than that email:
>> This proposal somehow went viral:
>> (includes an analyst quote)
>> (been a top trending story for the last week)
>> and lots more, in different languages around the world. If you search
>> “html6” on Twitter, you’ll see. There are hundreds or thousands of
>> shares, upvotes, comments, etc.
>> So it looks like a lot of people want something like this to happen. I
>> believe it represents web developers’ dissatisfaction in having to use
>> a part of the HTML spec, that is, dynamic loading of content. I put
>> this proposal out there as a result of my own frustrations with these
>> frameworks being constantly redesigned.
>> I’m checking if there’s any interest from the Webkit team on this? I’m
>> trying to plan the next steps and probably wouldn’t proceed without at
>> least some sort of interest or guidance from the browser vendors.
>> (maybe this is technically impossible, etc..) Next steps would
>> probably include working on a full spec, and possibly implementation. I
>> have built WebKit nightly before, but haven’t modified any of its code,
>> and I suspect something like this would be way beyond me time-wise to
>> fully implement myself, but if there’s interest, I could possibly figure
>> out some options.
>> Anyways do let me know of any interest.
>> Bobby Mozumder
>> FutureClaw Magazine
>> mozumder at futureclaw.com <mailto:mozumder at futureclaw.com> <mailto:mozumder at futureclaw.com <mailto:mozumder at futureclaw.com>>
>> www.futureclaw.com <http://www.futureclaw.com/> <http://www.futureclaw.com/ <http://www.futureclaw.com/>>
>> twitter.com/futureclaw <http://twitter.com/futureclaw> <https://www.twitter.com/futureclaw <https://www.twitter.com/futureclaw>>
>> www.linkedin.com/in/mozumder <http://www.linkedin.com/in/mozumder> <http://www.linkedin.com/in/mozumder <http://www.linkedin.com/in/mozumder>>
>> webkit-dev mailing list
>> webkit-dev at lists.webkit.org <mailto:webkit-dev at lists.webkit.org>
>> https://lists.webkit.org/mailman/listinfo/webkit-dev <https://lists.webkit.org/mailman/listinfo/webkit-dev>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the webkit-dev