[Sugar-devel] WebKit2 Browse - Download and Test

[Utkarsh Tiwari]

Hi,
    The errors which I am facing happened when I pulled the 'webkit2'
branch from https://github.com/sugarlabs/browse-activity.git I switched to
that branch and ran the browse. While tryig to access a page(like google.com),
browse is taking a lot of time and doesnt load the pages at all and
generates the log with the mentioned errors in the previou reply.

What would you all suggest me to do if I want to integrate a new feature
into the browse? Shall I modify the 'webkit2' (it contains BROWSE-158
version I guess..) branch or shall I simply push the PR to 'master' branch?

And where can I find the Browse-157.2?

Thanks,
Utkarsh
On Apr 27, 2016 12:45 PM, "Tony Anderson" <tony_anderson at usa.net> wrote:

> Hi Sam
>
> The goal of Utkarsh's project is to integrate Richa Sehgal's GSOC work
> with Browse. This was the original goal but at the time Gonzalo was not
> available.
> Ideally, an integration with 158 would save a step, I think it would not
> be helpful to use a development project to test webkit2. This is a critical
> feature because the webkit in 157.2 does not support flex - an essential
> feature in specifying layout for reponsive design. This is particularly
> important because browsers mistreat the Sugar screen resulting in poor
> matches between activities on an XO and the same activity on other laptops.
>
> Previous versions of webkit, so far as I know, followed the W3C guidelines
> for partial implementation of html5 and css3 - as Internet Explorer
> famously did not.
>
> Tony
>
> On 04/27/2016 02:43 PM, Sam Parkinson wrote:
>
> Hi Tony,
>
> 157.2 is not a very big release.  If you're not testing the WebKit2 port,
> it is probably not helpful for finding bugs in the webkit2 port.
>
> If you're involved in a deployment using comodity hardware, this is
> probably something that you want to look into.  While webkit2 is a big
> change, it is very important from a security and web-compatibility
> perspective.  Webkit1 is like internet explorer 8 - it hasn't been updates
> for like the last 5 years!
>
> Thanks,
> Sam
>
> On Wed, Apr 27, 2016 at 4:19 PM, Tony Anderson <tony_anderson at usa.net>
> <tony_anderson at usa.net> wrote:
>
> It may be expedient to test with Browse-157.2 which does not use webkit2
> for now. It is doubly hard to debug one change by using another
> software component under test.
>
> Tony
>
> On 04/27/2016 01:27 PM, Utkarsh Tiwari wrote:
>
> Hi,
>     I pulled the 'webkit2' branch from the browse-repo and after
> running the activity I am getting the errors ( can't load a page in
> browse) as shown in the attachment below.
>
> Thanks,
> Utkarsh Tiwari
>
> On 4/19/16, James Cameron <quozl at laptop.org> <quozl at laptop.org> wrote:
>
> Debian bug #802380 has a link that reproduces a "WebKit has crashed"
> dialog on Browse-158, for which I've attached a screenshot.
> http://www.reuters.com/article/2015/10/18/us-new-york-flightcenter-idUSKCN0SC14B20151018
>
> This was with 2.12.0, and it is probably a WebKit problem rather than
> a Browse problem, but it does expose some Browse problems in handling
> a WebKit crash ...
>
> - the cursor keeps spinning,
>
> - the home button doesn't work any more,
>
> - the stop loading button doesn't work either,
>
> - no evidence of the crash in the Browse logs.
>
> The activity stop button worked fine.
>
> On Sat, Apr 09, 2016 at 08:34:44PM +1000, sam at sam.today wrote:
>
> Hi All,
>
> I'm happy to release an unstable version of the WebKit2 browse.  Most
> things
> have been ported and many bugs fixed from the original port.  Please help
> by
> testing this!
>
> Special thanks to Gonzalo Odiard for his huge contribution to the port.
>
> Thanks,
> Sam
>
> =====
> Installing
> =====
>
> Note, this requires **WebKitGtk+ 2.11.3** or newer.  Practically, this
> means
> use Fedora 24+.
>
> You can install the activity from the git repository branch "webkit2":
> [1]https://github.com/sugarlabs/browse-activity/tree/webkit2
>
> You can use the XO bundle if you prefer:
> [2]https://people.sugarlabs.org/sam/
> Browse-158.xo
> (sha256sum
> 2cd0f96501eea9a5905d0f3bdc1fde88c85069e62d5eb7706f14f85a41b182b2)
>
> Then open Sugar and run the Browse activity.  Please verify that it has
> successfully installed version 158.
>
> Please report bugs somewhere.  You can email me <sam at sam.today> <sam at sam.today>, reply to
> this
> thread, or open them somewhere on bugs.sugarlabs.org.
>
> ==================
> What is good about WebKit2?
> ==================
>
> * Read the WebKit Security Advisories and feel happy that you are using
> WebKit2
> [1]
>     - Read "On WebKit Security Updates" and feel sad again (unless you
> run
> Fedora) [2]
> * WebGL Support (Hype!)
> * New javascript engine "FTL" (Faster Than Light) powered by the very new
> B3
> backend.  You can run Sugarizer even faster inside of Sugar!!
> * Web Process Separation keeps you safer from evil internet people.
>  Eventually, the web process will even be sandboxed from your system
> * Pinch-to-zoom support - real time text rendering while zooming (watch
> the
> lag!!)
> * GeoLocation support - web sites can request geo location permission
> * Notification support - web sites can request permission to send you
> notification
>
> =================
> Summary of Browse changes
> =================
>
> * Improve the autocomplete list (thanks to Utkarsh Tiwari)
> * PDF Tab Edge case fixes (thanks to James Cameron)
> *
> * New history format.  This is due to a change in WebKit2 api.
>   - You can open files made with old versions of browse.  However, it will
> only
> load the current tab page, not the full back/forward history list.
> * Print to PDF support removed.  This is due to a change in WebKit2 api.
> * Button to activate the Web inspector.
> * The long-press for palette code got even more dodgy.  It now fakes a
> right
> click - this is the only way to work with the webkit2 api changes.
>
> [1]  [3]http://webkitgtk.org/security.html
> [2]  [4]https://blogs.gnome.org/mcatanzaro/2016/02/01/
> on-webkit-security-updates/
>
> References:
>
> [1] https://github.com/sugarlabs/browse-activity/tree/webkit2
> [2] https://people.sugarlabs.org/sam/Browse-158.xo
> [3] http://webkitgtk.org/security.html
> [4]https://blogs.gnome.org/mcatanzaro/2016/02/01/on-webkit-security-updates/
>
> _______________________________________________
> Sugar-devel mailing listSugar-devel at lists.sugarlabs.orghttp://lists.sugarlabs.org/listinfo/sugar-devel
>
> --
> James Cameronhttp://quozl.netrek.org/
>
>
>
> _______________________________________________
> Sugar-devel mailing listSugar-devel at lists.sugarlabs.orghttp://lists.sugarlabs.org/listinfo/sugar-devel
>
>
>
>
> _______________________________________________
> Sugar-devel mailing list
> Sugar-devel at lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/archive/sugar-devel/attachments/20160427/089b5d9b/attachment.html>