Buttons disapear when placed above webobjects

Oct 07, 2014

Hi Just put Storyline 2 on my computer - yay!!!!

Already having a small issue - boo

At the moment I have a webobject with a button over top of it (one of the great new features and one I have always wanted to be able to do) but when the slide plays the webobject covers the button while you have the mouse over the webobject.

When you are over the menu or other parts of the slide the button appears.

This does make it impossible to press the button because it keeps disapearing when yo umove the mouse over to get to it.

Is there a setting that prevents this?

Any help appreciated

35 Replies
Helene Sobelman

I know this is an old thread... but i was having the same issue just now and happened upon the thread.  I agree with folks above... having the webobject come above other shapes on mouseover does take away from some of the usefulness.

I was just playing aroudn with some ideas from this thread and i seem to have gotten it to work if i put the webobject on the base layer then additional layers with shapes or hotspots or whatever i need and set those layers to "prevent user from clicking on baselayer"... so in effect the base layer becomes "an image" and you need to recreate any of the hyperlinks using hotspots.  The pro of using a webobject in this way would be that while it's acting as "an image".. at least it's a live image of the webpage each time you go .. to account for any updates..  the con is .. it's a live image .. so if there are changes to the layout of the page.. your hotspots may no longer be in the correct places.

...just thought i'd share my findings!

ahssan moshref

I agree with you Brett.


In this case having the content disappear above the web object means that someone did not ask the question what if that content is a button. How is user going to click on it when it disappear? A layer and its content should stay in its hierarchy unless it is being assigned to move up. 


Again I have to let go of a good design concept and create a not so user friendly course. It if frustrating to not be able to make the tools perform at the standard of one's design.  

Ashley Terwilliger-Pollard

Hi Ahssan,

This thread is a bit older, but the web object content will always appear at the front as detailed here. Our Product development team tries to think through a number of different use cases and scenarios, but we may not catch them all as folks can do things a number of different ways in Storyline. The behavior of the web object is not something that can be changed though, based on the way those elements are embedded.

If you have specific feedback about a behavior or way you'd prefer something to behave, I'd also advise sharing your thoughts with our team directly here. 

ahssan moshref

Hi Ashley.
Thanks for the reply.
As you mentioned the thread is a bit older. And I saw the problem being addressed in the Thread.
Which means that your team has not addressed the issues yet.
My need for a solution is urgent. I am currently working on a project and discovered this technical limitation.
And honestly I don't see the logic behind having WebObject appear above other layers that the designer intentionally places above the WebObject.



I understand that folks can do things a number of different ways.
But I can't find an alternative solution that will maintain the design and not cause other usability problems.
I will contact you team but most likely I will have to sacrifice the design again.


Ashley Terwilliger-Pollard

Hi Ahssan,

There isn't currently a change to the behavior as this is by design due to the nature of web objects and how they'll take precedent over other slide content - and although layers still on top of slides, they're still a part of the overall slide. You're welcome to reach out to our team and share your thoughts on this behavior but I think it's likely to be a situation of changing the design as you mentioned.

Hopefully others in the community will share the things they've done to also work with this behavior. 

This discussion is closed. You can start a new discussion or contact Articulate Support.