[news.eclipse.platform.swt] Re: Blocking all navigation and events to Br

[Mark Diggory <mdiggory@xxxxxxxxxx>]

Yes, I thought this as a solution, but found it unfavorable over simply 
being able to tell the difference between the events. Maybe even if the 
events generated also showed the method as well as the widget that was 
their source.

-Mark


Grant Gayed wrote:
> The LocationEvent does not differentiate between these two cases, but if you
> set the url or text into the Browser, you should be able to determine from
> the resulting callback that its location field matches the url that you just
> set in.
>
> Grant
>
> "Mark Diggory" <mdiggory@xxxxxxxxxx> wrote in message
> news:42A8CA3C.8090304@xxxxxxxxxxxxx
>
> > I have another question; Can this detect the difference between
> > traversing a link/form and a call to setUrl/setHtml? I only want to
> > block link traversal, not setUrl/Html.
> >
> > -Mark
> >
> >
> > Grant Gayed wrote:
> >
> > > Mark,
> > >
> > > You can veto or modify page changes in the changing event, as shown
>
> below:
>
> > > browser.addLocationListener(new LocationAdapter() {
> > >    public void changing(LocationEvent event) {
> > >        event.doit = false; /* veto link traversals */
> > >    }
> > > });
> > >
> > > Grant
> > >
> > > "Mark Diggory" <mdiggory@xxxxxxxxxx> wrote in message
> > > news:42A6EAFC.50607@xxxxxxxxxxxxx
> > >
> > >
> > > > Any takers? I think this has to be a common usecase?
> > > >
> > > > Mark Diggory wrote:
> > > >
> > > >
> > > > > I'm trying to use the Browser widget as a "Preview" of editor content.
> > > > > I'd like to block (and possibly override) the users ability to activate
> > > > > Links and form submit fields in the Browser so that they cannot
>
> navigate
>
> > > > > off of the page. What is the best way to approach this?
> > > > >
> > > > > thanks,
> > > > > Mark Diggory