While we do understand the value for your port in keeping these classes, WebKit
has never had any obligations to downstream ports and forks. Nothing is
stopping you from copying these files to your repository.
Gyuyoung, since nobody else has objected I think it’s fine to remove this.
It is part of the HTML specification:
Chrome seems to support it. It is also covered by the W3C web-platform tests.
Chris and Alexey seem to want to keep the feature because it is part of w3c
spec. I don't want to remove it if someone has any plan to use|enable it in
On Sat, Jan 30, 2016 at 2:51 AM, Chris Dumez wrote:
> It is part of the HTML specification:
22.12.2015, 09:02, "Gyuyoung Kim" :
> It looks like no ports have used a data transfer items feature. Even the
> feature hasn't been updated since 2011. If anyone doesn't have a plan to use
> it in future, I plan to remove it. Any objections ?
In Qt port
> DataTransfer.items is part of the spec, so it seems like we should
support it. Are you saying that the code that's currently in trunk is not
useful enough to help with eventually adding full support?
No, current implementation seems to support the spec. If some ports want to
use it, current
It looks like no ports have used a data transfer items feature. Even the
feature hasn't been updated since 2011. If anyone doesn't have a plan to
use it in future, I plan to remove it. Any objections ?
webkit-dev mailing list
Mail list logo