330553 - Show link in statusbar when hovering over a trigger with a load

Status: RESOLVED WONTFIX

(Core Graveyard :: XForms, enhancement)

Description

[Allan Beaufour]

If you use a trigger + load then you lack the "normally expected" link in the statusbar, like when you use an a tag.

This might be troublesome to make work, at least in the general case, so this might be WONTFIX.

One of the problems is that a trigger might contain any number of action elements, including multiple loads. Inside action tags, etc. etc. So as a start, if there are more than one load -- which one should we show? And if we choose the first one, the form author can trick the user by having:
<xf:trigger>
  <xf:label>Click me and win a zillion bucks</xf:label>
  <xf:load src="http://evil.com/"/>
  <xf:load src="http://good.com/" ev:event="DOMActivate"/>
</xf:trigger>

So maybe we could bind behaviour only to
trigger > label + load[ev|event="DOMActivate"]
?

Ideas and suggestions are welcome. This is just a brainstom from my part...

Comment 1

[Allan Beaufour]

Attachment: Testcase

Comment 2

[aaronr]

(In reply to comment #0)
> If you use a trigger + load then you lack the "normally expected" link in the
> statusbar, like when you use an a tag.
> 
> This might be troublesome to make work, at least in the general case, so this
> might be WONTFIX.
> 
> One of the problems is that a trigger might contain any number of action
> elements, including multiple loads. Inside action tags, etc. etc. So as a
> start, if there are more than one load -- which one should we show? And if we
> choose the first one, the form author can trick the user by having:
> <xf:trigger>
>   <xf:label>Click me and win a zillion bucks</xf:label>
>   <xf:load src="http://evil.com/"/>
>   <xf:load src="http://good.com/" ev:event="DOMActivate"/>
> </xf:trigger>
> 
> So maybe we could bind behaviour only to
> trigger > label + load[ev|event="DOMActivate"]
> ?
> 
> Ideas and suggestions are welcome. This is just a brainstom from my part...
> 


A useful feature, but like you said...tough to make work well for every scenario.  Also, we'd have to look for ev:event="click" handlers too, right?

Comment 3

[alexander :surkov (:asurkov)]

There is one more issue when xforms are used not in the browser but as separate application.

Comment 4

[Allan Beaufour]

(In reply to comment #3)
> There is one more issue when xforms are used not in the browser but as separate
> application.

As long as it has window.statusbar ... or whatever the object is called, that will be solved by this too then.

Comment 5

[David Bolter [:davidb] (NeedInfo me for attention)]

RIP xforms