Hey Brendan and Dave,

OK so that's 2 occurrences of this now... there's gotta be something amiss here!

Since I can't replicate it locally, wondering if anything else could be impacting it? e.g. another data-type or package?

@Brendan - could you let me know which version of Umbraco and uComponents - and which web-browsers this happens on?

Would love to get to the bottom of this and get a fix out there.

Thanks, Lee.

Hi Lee,

please find the details you asked for below. Cheers for the help btw.

B

umbraco v 4.7.2 

uComponents 3.1.2.3

OK a bit more info on this. It looks fine when the viewport is smaller, I have a high res monitor and when the browser window is full size it causes the issue.

I am going to makr your answer as solving it Dave, it would be great to get the actual problem fixed in Core if it is still happening. I will keep an eye out for it in the next project I start with 4.8.

Cheers for the help.

B

Brendan and Dave, what screen resolution are you using?

Thanks, Lee.

1920 x 1200

i got the same

I still can't replicate the bug! :-(  I'm on dual monitors (1680x1050 and 1600x900) ... even if I try to stretch the window across both screens and reload MNTP, I can't reproduce the error.

If anyone wants to supply a fix, that would be much appreciated!  *hint*hint* Ismail is part of uComponents team ;-)

Cheers, Lee.

I wasn't encountering this on Friday.

I installed VS 2012 (which also installs asp.net 4.5) on the weekend.

I encountered this problem today.

My colleage wasn't encountering this problem on the exact same codebase, running on the exact same database - he hadn't installed VS 2012 or .net 4.5

We tried running the codebase on a new Windows 8 VM that is running VS 2012 - and boom, encountered the problem.

Seems that the style rule that is pushing the layout all funny was coming from a set of WebResource.axd, adding a width of 622 pixels to the .multiNodePicker .header selector.  Killing those rules in Firebug pushed the layout back to normal(ish).

Hope this helps! Would be good to have an official fix rather than the proposed workaround extra styling (which we'll do for the short term)

Just to chip in here:

I have a 4.7.2 installation that just started doing this - and I have no idea what triggered it.

I'm on a MacBook Pro @ 1440x900, and using Safari 6 (OS X Mountain Lion) - using the Web Inspector I can see that the rule .multiNodePicker .left.propertypane is set to clear: none, – either removing this or specifically setting it to clear: both will fix the issue...

** off to codeplex...

/Chriztian

I have applied the CSS fix for MNTP in both uComponents (v3.x, v4.x) and Umbraco core (upcoming v4.9).  Since I still can't replicate this issue, would any one be willing to help me test the patch?

(If you don't already have my email address, get in touch via: http://j.mp/leeeeee - I'll send over the latest DLL)

Thanks, Lee.

I think you might have fixed this already, but FWIW I think the issue is to do with the order that the css files 

/umbraco_client/propertypane/style.css and /umbraco_client/tabview/style.css are loaded.  

If tabview/style.css is loaded after propertypane the 

float: left; 

in .header overrides

float: none;

in .propertypane on the element

<div class="header propertypane">

This also causes some different styling to occur as the background property of .header will also take precedence.

That said, I'm not sure what affects the order of the stylesheets as they are both loaded by ClientDependency attributes. This might explain why the problem is intermittent (if there is nothing special dictating which css file is loaded first)

Stephen

Hi all,

I had this CSS "bug" aswell a week ago when fooling around with a Umbraco 4.9 install.

The problem started to occur when I installed uComponents (the package) and did the legacy-folder workaround. I haven't got the faintest idea if that has got something to with it, but when I reinstalled Umbraco 4.9 (due to other reasons than uComponents) and I didn't install the uComponents package, everything was fine again.

- Bo

Hi, 

I have encountered the same issue as well.

I did find using the DAMP package for images, had an effect on the mntp, but in a strange way.

I had set my tabs up as, Content, Side Column, Main Banner.

Placing the MNTP in any tabs had the bugged layout, but placing DAMP on the first "Content" tab, somehow fixed the layout issue.

Ive tried adding the CSS to the umbraco/client/ui/default.css but with no effect.

Anyone know how to get the css fix to work?

Thanks 

Did you add your fix to umbraco_client/ui/default.css (with an underscore) as you've said umbraco/client/ui/default.css (with a forward slash)?

The strange way the bug appears is to do with the order the two css files (propertypane/style.css and tabview/style.css) are loaded, having DAMP on different tabs must be triggering the client dependcies in different orders.

I haven't looked what fix has been added to uComponents but there probably needs to be similar css to the one posted above that dictates which styles take preference on the class="header propertypane" div as depending on which css file loads first it affects the positioning and background of the element.

Stephen

Just saw this issue for the first time ever on a 4.7.0 installation with uComponents 2.1 installed.

The weird thing is that it looks fine on our staging environment but all of the sudden the issue happened on the live environment last week and nothing has changed on the site for a month...It's a bit hard to explain this to the boss and the client.."Something has been changed! I wanna know what!"....argh...:-/

But happy to see it's fixed in newer releases though :)

It's just so weird that it happens out of nowhere???

/Jan

Ok, so it turns out that in my setup I needed to do the following to quickfix the issue:

1: Go to /umbraco_client/ui/default.css

2: Add the following

.multiNodePicker .left.propertypane{
clear: both !important;
}

3: Empty the ClientDependency cache in /App_Data/TEMP/ClientDependency

4: Increment the version number in /config/ClientDependency.config

Perhaps step 3 can be omitted but by doing it this way all suspetcs are eliminated and the change will take effect.

To sum it up I'm running Umbraco 4.7 with uComponents 2.1 installed.

Hope this comes in handy for somebody else a some point :)

/Jan

is working on a reply...