Support Forum

working.gif is permanent there

DH David H
David H
Member

Hi,

I think there is a small bug, but maybe I did somewhere a mistake…

In the admin small bar, where you have links to – spam, unread posts and posts that are waiting for permission,

under the id “spAdminQueue”,

there is an image with the name- “working.gif“

I think it so pose to be there only when the bar is on loading.

by me it is there the all the time…

thanks and

Happy new year

David

5 Answers

New Answer

MP Mr Papa
Mr Papa
Member

sounds like a js conflict…  its hidden by default then enabled, and finally removed..  if its not hidden at start, wonder if something else is ‘showing’ it… can you inspect the css on page load?

DH David H
David H
Member

I looked allover and im not sure what i see…

 

The image has a class- spInlineSection

In the css it is display:none but with no effect. It works with !important.

The image has also an id- spBarSpinner

This id doesn’t have any css.

I think that the JS from the admin tools communicate with the id spBarSpinner

 

So I add this to my css:

#spMainContainer #spBarSpinner {
display: none !important;
}

It needed the !important…

 

It works but I hope i didn’t cause any problem somewhere els…

 

YS Yellow Swordfish
Yellow Swordfish
Member

The class ‘spInlineSection’ is used extensively throughout SP so it would be worth trying to discover why the ‘display:none’ rule is not being honoured as it should be.

But I believe the rule is always set up when this class falls within the ‘spMainContainer’ id so it should really be safe from outside interference.

Which leaves me with no real idea why it should be ignored but a feeling that it should be tracked down. So let’s start with the obvious…. might this – by some bizarre and weird coincidence – be used in any other CSS being loaded?

YS Yellow Swordfish
Yellow Swordfish
Member

Have you looked at this using a browser console – or a tool such as Firebug? This would show you exactly what CSS is – in reality – being applied and should show up why the standard CSS is being overridden. At least I would expect it to…