Opened 12 years ago

Last modified 11 years ago

#3512 closed defect

'about:blank' is not handled properly, is not finishing the loading — at Version 8

Reported by: HoboPrimate Owned by: erikos
Priority: Unspecified by Maintainer Milestone:
Component: Browse Version: 0.95.x
Severity: Unspecified Keywords: 12.1.0, patch, olpc-test-passed
Cc: manuq, humitos Distribution/OS: Fedora
Bug Status: Unconfirmed

Description (last modified by manuq)

As consequence, new tab shows small progress bar in the adress, and says "Loading..." at the bottom.

Test Case:

Open a new tab, you'll see a small progress bar in the adress bar. It will also say "Loading..." at the bottom.

Other test:

Write 'about:blank' in the URL entry and hit enter, same behaviour.

Browse 135

Change History (10)

comment:1 Changed 12 years ago by callkalpa

With the patch the new tabs will say "Ready"

comment:2 follow-up: Changed 12 years ago by garycmartin

I thought these "Loading..." and URL messages in the bottom left of the screen were debug text messages while testing web kit, not an intended Browse feature to ship. At the very least they are rather distracting, not Sugar like, do not work for touch enabled devices (i.e. no ability to hover a cursor over a link), and should at best only appear if you delay hover over a link.

The "Loading..." message is superfluous to the design, that is what the Browse loading progress bar is there to indicate...

comment:3 in reply to: ↑ 2 ; follow-up: Changed 12 years ago by callkalpa

Replying to garycmartin:

I thought these "Loading..." and URL messages in the bottom left of the screen were debug text messages while testing web kit, not an intended Browse feature to ship. At the very least they are rather distracting, not Sugar like, do not work for touch enabled devices (i.e. no ability to hover a cursor over a link), and should at best only appear if you delay hover over a link.

The "Loading..." message is superfluous to the design, that is what the Browse loading progress bar is there to indicate...

In the case where it takes a lot of time to load and the progress bar takes a considerable time to show a significant change (specially at the very beginning), still the user will know that the page is loading.

comment:4 in reply to: ↑ 3 ; follow-up: Changed 12 years ago by garycmartin

Replying to callkalpa:

Replying to garycmartin:

I thought these "Loading..." and URL messages in the bottom left of the screen were debug text messages while testing web kit, not an intended Browse feature to ship. At the very least they are rather distracting, not Sugar like, do not work for touch enabled devices (i.e. no ability to hover a cursor over a link), and should at best only appear if you delay hover over a link.

The "Loading..." message is superfluous to the design, that is what the Browse loading progress bar is there to indicate...

In the case where it takes a lot of time to load and the progress bar takes a considerable time to show a significant change (specially at the very beginning), still the user will know that the page is loading.

A graphical spinner in the Tab can be used to avoid localisation of the word "Loading...", or the word Loading... could be the Tab name while loading, or a graphical spinner could be shown in the middle of the loading canvas space (ideally composited over whatever page is there, but it could be a solid rectangle with a spinner on it).

comment:5 in reply to: ↑ 4 Changed 12 years ago by callkalpa

Replying to garycmartin:

Replying to callkalpa:

Replying to garycmartin:

I thought these "Loading..." and URL messages in the bottom left of the screen were debug text messages while testing web kit, not an intended Browse feature to ship. At the very least they are rather distracting, not Sugar like, do not work for touch enabled devices (i.e. no ability to hover a cursor over a link), and should at best only appear if you delay hover over a link.

The "Loading..." message is superfluous to the design, that is what the Browse loading progress bar is there to indicate...

In the case where it takes a lot of time to load and the progress bar takes a considerable time to show a significant change (specially at the very beginning), still the user will know that the page is loading.

A graphical spinner in the Tab can be used to avoid localisation of the word "Loading...", or the word Loading... could be the Tab name while loading, or a graphical spinner could be shown in the middle of the loading canvas space (ideally composited over whatever page is there, but it could be a solid rectangle with a spinner on it).

A graphical spinner like in firefox will look nice

comment:6 Changed 12 years ago by manuq

  • Cc manuq added

comment:7 Changed 12 years ago by humitos

  • Cc humitos added

I was researching about this problem.

I found that the progress bar, webkit and our browser work good. I mean, there is no problem neither with the "progress" value of the webkit nor with opening a new tab as we (manuq and I) thought; instead the problem is with the "about:blank" page.

Try this:

  1. Open Browse, you will see the sugar labs page by default
  2. Go to the URL address bar and type: "about:blank"
  3. You will see the "Loading.." at the bottom and you will see the progress bar in the 10%, right?

Well, the problem here is that webkit stops in this status: "<enum WEBKIT_LOAD_PROVISIONAL of type WebKitLoadStatus>" with progress in 0.1 (10%) and it never gets the "<enum WEBKIT_LOAD_FINISHED of type WebKitLoadStatus>" status with progress in 1.0 (100%)

So, the question is: why when you open "about:blank" webkit never gets the FINISHED status?

Changed 12 years ago by humitos

manuq's test

comment:8 Changed 12 years ago by manuq

  • Description modified (diff)
  • Summary changed from New tab shows small progress bar in the adress, and says "Loading..." at the bottom to 'about:blank' is not handled properly, is not finishing the loading
Note: See TracTickets for help on using tickets.