Skip to main content
AP_AW
AP_AW
Inspiring
August 8, 2016
Answered

Covered button still clickable

  • August 8, 2016
  • 2 replies
  • 1203 views

A button that I'd covered with an image still caused the cursor to change to a hand and still responded to a mouse click. I believe that in HTML it's normal/expected that a mouse click event on one element doesn't bubble/capture to a separate element unless those elements are nested. I doubt Captivate nests a DIV within an IMG so I guess Captivate is doing something with Canvases or tracking the click coordinates instead of the targets to (in my opinion) decrease usability.

I find the behaviour confusing. Does anyone know why it works like that?

This topic has been closed for replies.
Correct answer Lilybiri

Covering an interactive object with a static object never deactivated the interactive object in any version of Captivate that I used. Since I'm not a programmer, I cannot explain why but sometimes this can be really interesting.

I experienced some us cases where this wasn't the case for HTML output, but always for SWF output. Instead of covering up the interactive object, you need to disable the interactive object or hide it.

2 replies

A
Andy VanWag
Participant
November 18, 2019

I think this should be considered a bug. The web app that I'm designing uses pop-up modals (a pretty common thing). When a pop-up comes on screen everything behind it is darkened (I put a transparent black rectangle between the pop-up and everything else). When someone is previewing the prototype I don't want them to be distracted by clickable links in the background when there is a pop-up present. 

 

Ignore the ugly dark blue rectangles. That was just me trying to redact some information.

 

Clicking on something that is covered up in the background throws off the entire flow of the prototype. Now I understand that this is just one scenerio and some people may want to have things clickable even when they are covered up (even though I can't think of a reason why). So maybe this should be an option that you can toggle on and off.

 
 
Lilybiri
Lilybiri
Legend
November 19, 2019

I have explained in my answer what happens. You may consider it to be a bug, but probably engineers will say it is by design. There is a command 'Disable' which you can use to make the button or other interactive object disabled temporarily. Covering up has never been a good practice, even with SWF output. In Fluid Boxes it is even impossible to stack.

Launch a bug report if you want to do so.

Lilybiri
LilybiriCorrect answer
Legend
August 8, 2016

Covering an interactive object with a static object never deactivated the interactive object in any version of Captivate that I used. Since I'm not a programmer, I cannot explain why but sometimes this can be really interesting.

I experienced some us cases where this wasn't the case for HTML output, but always for SWF output. Instead of covering up the interactive object, you need to disable the interactive object or hide it.

AP_AW
AP_AWAuthor
Inspiring
August 8, 2016

Thanks for confirming another Captivate usability "flaw" for me ;-)

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices