Opened 12 years ago

Last modified 8 years ago

#3547 assigned defect

Browse: webkit spawns multiple scrollbars in some google apps

Reported by: greenfeld Owned by: humitos
Priority: Low Milestone:
Component: Browse Version: Unspecified
Severity: Minor Keywords: 13.1.0, upstream, wk2fix
Cc: manuq Distribution/OS: OLPC
Bug Status: Unconfirmed

Description (last modified by manuq)

On some webpages (such as news.google.com) Browse will show the Sugar-style scrollbar, as well as an additional scrollbar immediately to the left of the first one.

This has been seen on XO-1.5 and XO-1.75 with OLPC 12.1.0 os8. Also seen in Epiphany, so it's a WebKit issue.

Attachments (2)

browse-scroll-bar.jpeg (246.1 KB) - added by humitos 12 years ago.
13.png (121.4 KB) - added by manuq 12 years ago.

Download all attachments as: .zip

Change History (16)

Changed 12 years ago by humitos

comment:1 Changed 12 years ago by manuq

  • Milestone changed from Unspecified by Release Team to 0.98
  • Severity changed from Unspecified to Minor

This seems very specific to google apps, I can see it in plus and news. Setting as minor bug and posponing to 0.98.

comment:2 Changed 12 years ago by manuq

  • Owner changed from erikos to manuq
  • Status changed from new to assigned

Changed 12 years ago by manuq

comment:3 Changed 12 years ago by manuq

Same happens in Epiphany, screenshot attached.

comment:4 Changed 12 years ago by manuq

  • Priority changed from Unspecified by Maintainer to Low

comment:5 Changed 12 years ago by manuq

Added a ticket in Epiphany bug tracker: https://bugzilla.gnome.org/show_bug.cgi?id=676982

comment:6 Changed 12 years ago by manuq

  • Description modified (diff)
  • Summary changed from Browse may spawn multiple scrollbars to Browse: webkit spawns multiple scrollbars in some google apps

comment:7 follow-up: Changed 12 years ago by dsd

  • Keywords 13.1.0 added; 12.1.0 removed

The scrolled window (with the main scroll bars) is owned by Browse, and the google-specific scroll bars are owned by WebKit. There needs to be some communication between the two so that Browse hides its scroll bars when necessary.

Have we tried working with this API?
http://webkitgtk.org/reference/webkitgtk/stable/WebKitWebWindowFeatures.html#WebKitWebWindowFeatures.description

comment:8 Changed 12 years ago by humitos

  • Cc humitos added

comment:9 Changed 12 years ago by manuq

  • Cc manuq added; humitos removed
  • Owner changed from manuq to humitos

comment:10 in reply to: ↑ 7 Changed 11 years ago by humitos

  • Milestone changed from 0.98 to 1.0

Replying to dsd:

Have we tried working with this API?

I've just tried this:

window_features = self.get_window_features()
window_features.connect('notify::scrollbar-visible',
                        self.__scrollbar_visible_cb)
window_features.connect('notify::statusbar-visible',
                        self.__scrollbar_visible_cb)
window_features.connect('notify::toolbar-visible',
                        self.__scrollbar_visible_cb)
window_features.connect('notify::menubar-visible',
                        self.__scrollbar_visible_cb)
window_features.connect('notify::locationbar-visible',
                        self.__scrollbar_visible_cb)
self.props.window_features = window_features

but those signals are not emitted when I go to http://news.google.com for example, and that page shows its own scrollbar + Browse's Activity one.

comment:11 Changed 11 years ago by humitos

This email says that gmail does some tricks with the scrollbars and that is why we are having this issue. I'm not sure how to solve it yet and actually I don't know if it there is a solution.

http://www.mail-archive.com/webkit-gtk@lists.webkit.org/msg00504.html

In the same email this guy talks about 'frame-flattening':

http://webkitgtk.org/reference/webkitgtk/stable/WebKitWebSettings.html#WebKitWebSettings--enable-frame-flattening

comment:12 Changed 11 years ago by manuq

  • Keywords upstream added

comment:13 Changed 11 years ago by dnarvaez

  • Milestone 1.0 deleted

Milestone 1.0 deleted

comment:14 Changed 8 years ago by SAMdroid

  • Keywords wk2fix added

This has been fixed in epiphany webkit 2.

Should be fixed with browse webkit 2.

Note: See TracTickets for help on using tickets.