[webkit-qt] html 5 progress element and web sockets in the 2.0 release

[Antti Koivisto]

At least the progress element seems unlikely to cause any harm with
existing contents. Enabling it would potentially give some real life
test coverage, making it better in the next release.


  antti

On Thu, Apr 1, 2010 at 3:56 PM,  <Yael.Aharon at nokia.com> wrote:
>
>   Hi,
>   I agree with Henry, both items can be disabled in QtWebKit 2.0.
>   -Yael
>
>   -----Original Message-----
> From: webkit-qt-bounces at lists.webkit.org [mailto:webkit-qt-bounces at lists.webkit.org] On Behalf Of Hausmann Simon (Nokia-D-Qt/Oslo)
> Sent: Tuesday, March 30, 2010 6:03 AM
> To: webkit-qt at lists.webkit.org
> Subject: Re: [webkit-qt] html 5 progress element and web sockets in the 2.0 release
>
>   On Friday 26 March 2010 Haverinen Henry (Nokia-D-Qt/Oslo), wrote:
>   > Hi everyone,
>   >
>   > If we include these in the release, it'd be extremely good to have a
>   > documented test plan to show how they've been tested, as a sub-task in the
>   > JIRA item.
>   >
>   > The JIRA item for web sockets is QTWEBKIT-46. There's no JIRA item for the
>   > progress element.
>   >
>   > My understanding is that the work for both items has been targetting at
>   > release 2.1, so it should be fine to disable them in 2.0, reduce the risks
>   > in that release, and put all bug fixing focus on the existing features.
>
>   Yael, Laszlo: Any opinion? :)
>
>
>
>   Simon
>
>   > On Mar 26, 2010, at 12:50 PM, ext Simon Hausmann wrote:
>   > > Hi,
>   > >
>   > > both of the features in the $subject are enabled by default in the
>   > > release.
>   > >
>   > > I understand that the progress element is work in progress :). Should we
>   > > disable it in the branch or cherry-pick all fixes for it?
>   > >
>   > >
>   > > What about WebSockets?
>   > >
>   > > Currently they don't handle SSL errors, i.e. if the SSL handshake fails
>   > > because of a man-in-the-middle attack with a forged certificate, then we
>   > > ignore the errors and continue to establish the connection. I've created
>   > > https://bugs.webkit.org/show_bug.cgi?id=36655 to track this issue.
>   > >
>   > > That makes me think we should either disable it for fix it for the
>   > > release. What do you think?
>   > >
>   > >
>   > >
>   > > Simon
>   > > <signature.asc><ATT00001..txt>
>   >
>   > _______________________________________________
>   > webkit-qt mailing list
>   > webkit-qt at lists.webkit.org
>   > http://lists.webkit.org/mailman/listinfo.cgi/webkit-qt
> _______________________________________________
> webkit-qt mailing list
> webkit-qt at lists.webkit.org
> http://lists.webkit.org/mailman/listinfo.cgi/webkit-qt
>