thx i'll try it,
until now i thought normal html works flawlessly within gwt webapp but in
this case i am disabused.
On Saturday, 22 September 2012 17:09:30 UTC+2, Andrei wrote:
Something like this:
myHTMLWidget.addClickHandler(new ClickHandler() {
@Override
public void
can you explain how to use the html5 feature you mentioned?
On Friday, 21 September 2012 16:55:51 UTC+2, Jens wrote:
Have you tried to attach an event listener (DOM.addEventListener()) to
these anchors and call ClickEvent.preventDefault() when you click on them?
That could suppress the
Someone else already explained it ;-)
http://carlosaguayo.posterous.com/html5-history-in-gwt
Also read the two comments on that page.
-- J.
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To view this discussion on the web visit
That's quite something. The hashtag was originally meant for the use
tanteanni intends (jumping to points within a document), but it's been so
heavily abused that we now have to write workarounds to get the original
behaviour back.
On Friday, September 21, 2012 4:55:51 PM UTC+2, Jens wrote:
I think it is possible to attach a single ClickHandler to the HTML widget
containing the HTML document. When clicked call preventDefault(), as Jen
suggested, look at the source of the click, and if it is your anchor,
scroll to the cursor position.
On Friday, September 21, 2012 10:55:51 AM
Something like this:
myHTMLWidget.addClickHandler(new ClickHandler() {
@Override
public void onClick(ClickEvent event) {
event.preventDefault();
Element e = Element.as(event.getNativeEvent().getEventTarget());
if (e.getAttribute(href).contains(#)) {
This question could also be answered
herehttp://stackoverflow.com/questions/12509969/gwt-and-in-page-hyperlinks-chapter3-interfere-with-history-tokens
:-).
I want to add a html-document to a view. the html page contains an toc with
anchors a href=#Chapter1Chapter 1/a and a
I'm not quite sure what you are trying to do. If your hrefs are meant to
be page request then lose the hash. However if your hrefs are truly meant
to be targeted as history tokens then you can try something like :
g:InlineHyperlink targetHistoryToken=chapter1
ui:field=simpleTabChapter
Have you tried to attach an event listener (DOM.addEventListener()) to
these anchors and call ClickEvent.preventDefault() when you click on them?
That could suppress the history change and you can scroll your html
document yourself by reading the href attribute and searching the anchor
you
