ipsGlobalNotification needs to hide or update rather than fade when triggered while visible

crud, 3.3.4, but id bet this would happen on any 3.2.x+... is a timing thing, currently and previously just making my Javascript do nothing if it is on-screen.... it is that Fade call doing it.

/* Already one open? */
if ( $('ipsGlobalNotification' ) )
{
var span = $('ipsGlobalNotification').down('span');

/* fade out current content and fade in new */
new Effect.Fade( span, { duration: 0.8, afterFinish:
function() {
	 span.replace( new Element( 'span' ).update( content ) );
	 new Effect.Appear( $('ipsGlobalNotification').down('span'), { duration: 0.8 } );
}
} );
}

ergo, at that instant it is on-screen, but not visible or is 'fading', the js err pops.... seems more wise to fade it out(the whole notification)actually remove it and make a new one fade in frankly.... thinking its the inability to down to the span as the notification is not visible.

/* Already one open? */
if ( $('ipsGlobalNotification' ) )
{
var span = $('ipsGlobalNotification').down('span');
if(!span){return;}

Would be the cheap fix similar to what I’m doing in my js.

Updating Status to: Awaiting Feedback
Updating Version to: 3.3.4

I'm having difficulty following what you are trying to explain. Could you please post steps to reproduce this issue so I can see it first hand?

I'm having difficulty following what you are trying to explain. Could you please post steps to reproduce this issue so I can see it first hand?

update your status, open it again and update it before the notification fully fades... though what I am reporting is factually hard to hit... or just put this somewhere and click,

<span id='globalNotifyTester' class='ipsButton'>
Click me
</span>
<script type='text/javascript'>
document.observe("dom:loaded", function(){
$('globalNotifyTester').observe('click', function()
{
var rand = Math.random();
ipb.global.showInlineNotification( rand );
});
});
</script>

Also.... as far as I can see its not being updated properly anyway, hence why everybody has code stopping input when visible.

Yeah you've still lost me I'm afraid .

1) open user menu and update staus (inline alert appears)
2) open menu again and update before inline alert fades out.

http://screencast.com/t/WFFYTcHz1wS

What am I missing?

that the message must differ? timing?
is evil to reproduce frankly, but i have hit it often enough in ajax calls to make me stop the fire when that is visible.
Can I just change what this report is about?
try the above code, the span is factually not updating properly with the new message... causes this sort of stuttering effect whereby only the first message is shown.
I suppose this would be better titled kill it(the element/timeout/reference) and make a new one, it is just not updating the message properly.

Updating Status to: Cannot Reproduce

-

does the above code properly update the message for you? it not doing so(the message not updating, and thus stuttering) is consistently reproducible(at least in Firefox) in any usage that changes the message, you test with a static single message, correct?
Either the code attempting to update the notification is unnecessary and should be removed if it was never meant to, or it should be changed to update properly.

Updating Status to: Confirmed - Skin Issue

OK so what you're saying is if the inline global notification message is triggered and then something else triggers it with different text then the new message will not show?

yes and general muckiness follows as a result.

Updating Fixed In to: 3.4.0
Updating Status to: Fixed

OK, what will happen now is this:

 

- First notification shows up

- Another one fires while the first is open, so the first fades out immediately, and the second appears afterwards

- The second is visible for the normal length of time