[Webkit-unassigned] [Bug 19360] New: Frags on current page don't generate "navigation-requested" events
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Mon Jun 2 11:17:08 PDT 2008
http://bugs.webkit.org/show_bug.cgi?id=19360
Summary: Frags on current page don't generate "navigation-
requested" events
Product: WebKit
Version: 526+ (Nightly build)
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: Normal
Priority: P2
Component: WebKit Gtk
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: Don at Scorgie.org
CC: alp at nuanti.com
While trying to make yelp (the GNOME help browser) work with Webkit, I've hit
the following issue (copy-paste of an email I originally sent to Alp directly):
I've uploaded an example program to:
http://www.gnome.org/~dscorgie/webkit_frags.c
The basic problem is that anchor points to current documents sometimes
doesn't emit a "navigation-request" signal.
The example program (compiled with:
gcc -o main webkit_frags.c `pkg-config --cflags --libs webkit-1.0`
) produces a page with 2 anchors and 2 links in it. The first link
looks like:
<a href="#link1">
while the second looks like:
<a href="out.xhtml#link2">
When run without parameters, the example will set the base URI to:
"file://out.xhtml". In this case, clicking the first link will move to
the corresponding anchor, but not generate the "navigation-requested"
event (as denoted by a message to stdout).
The program can take a second parameter, which specifies the base URI.
If this is set to:
"out.xhtml", the navigation-requested signal is generated, but the page
doesn't jump.
"/out.xhtml" the navigation-signal is NOT generated and the page jumps.
"file:out" the navigation-signal is NOT generated and the page jumps.
"out" the navigation-signal is generated, but the page doesn't jump.
Anyway, the basic pattern seems to be a signal is only generated when
the base URI doesn't contain a ":" or "/" character.
This is a bit of a problem for us as gnome-doc-utils (which generates
our xhtml) tends to create links using "#frag" for pages in the same
document, but not on the same page. The way we get around this is to
intercept links clicked and handle them ourselves.
Long ramblings later, I'm done. Any help with this would be
appreciated.
--
Configure bugmail: http://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
More information about the webkit-unassigned
mailing list