Re: [webkit-dev] All development moved private?

[Randall Bennett]

Sorry for the presumptions which were offensive. I had previously followed
discussions on email as the main way to see what was coming to Webkit. When
that changed (pretty dramatically imo) I was concerned and I could have
sought out the other places before speculating.

Sorry!


On Fri, Jul 12, 2013 at 11:04 AM, Ryosuke Niwa ryosuke.n...@gmail.comwrote:

 On Fri, Jul 12, 2013 at 10:55 AM, Randall Bennett 
 randall.benn...@gmail.com wrote:

 I've noticed this list has basically gone silent.


 Why would you say that? There were 145 posts in May 2013 and 133 posts in
 June 2013 to webkit-dev.

 While it's true that we have less posts now (there were 376 posts in May
 2012 and 433 posts in June 2012), that's hardly silent.

 I'm wondering if there's another place where I can find out about what's
 being developed with Webkit, or if Webkit's public development has
 essentially ceased now that Google has forked Blink.


 Neither of those speculations is true.

 - R. Niwa


___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev

Re: [webkit-dev] HbbTV support within Webkit

[Randall Bennett]

On Thu, Oct 11, 2012 at 12:16 PM, Maciej Stachowiak m...@apple.com wrote:


 On Oct 11, 2012, at 7:40 AM, Mark Toller mark.tol...@samsung.com wrote:

  -Original Message-
  From: Dominik Röttsches [mailto:dominik.rottsc...@intel.com]
 
  On 10/10/2012 10:26 AM, Mark Toller wrote:
  What we would like to see initially is Webkit based browsers (Chrome,
  Safari, Minibrowser, etc) actually load HbbTV pages instead of asking
  the user to download the content - this would indirectly benefit the
  end goal of Webkit (to get everyone to support standard W3C/HTML5)...
 
  This particular change is just a matter of adding one more displayable
  mime-type, right?
 
  Almost. I've created a bug and patch for this particular change:
 
  https://bugs.webkit.org/show_bug.cgi?id=99049
 
  As someone else stated, I think the best approach is to create
  a bug for each change we consider worthwhile, and then they can be
  considered individually.

 I don't think we should take this change or accept this feature in
 general. It seems that of those who have spoken up, the WebKit community is
 not in favor of this direction.



 Even though the specific change in that patch is relatively small,
 supporting custom MIME types has significant disadvantages:

 - Creates interoperability issues with other browsers.
 - Fragments the web
 - Opens us up to further requests to add support for similarly niche MIME
 types in the future

 If CE-HTML and HbbTV content is fine to process as ordinary HTML, then it
 should be served with text/html MIME type. That would avoid all of these
 problems. If a consortium decided to create custom mime types instead, then
 they made a mistake and should fix it. In some cases, when the technology
 is compelling or there is a wealth of existing content, we live with
 arguable errors in the standard. But neither of those considerations
 applies here.

 Regards,
 Maciej

 ___
 webkit-dev mailing list
 webkit-dev@lists.webkit.org
 http://lists.webkit.org/mailman/listinfo/webkit-dev



 +1. As someone who builds applications specifically for TV producers, I
feel that this custom mime type is the first in a series of bad moves.

Why doesn't the HBB group form its own W3 style group? I think this is just
heading in the wrong direction.

rb
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo/webkit-dev