Deliver Awesome UI with the most complete toolboxes for .NET, Web and Mobile development
Automate UI, load and performance testing for web, desktop and mobile
A complete cloud platform for an app or your entire digital business
Detect and predict anomalies by automating machine learning to achieve higher asset uptime and maximized yield
Automate decision processes with a no-code business rules engine
Optimize data integration with high-performance connectivity
Connect to any cloud or on-premises data source using a standard interface
Build engaging multi-channel web and digital experiences with intuitive web content management
Personalize and optimize the customer experience across digital touchpoints
Build, protect and deploy apps across any platform and mobile device
Rapidly develop, manage and deploy business apps, delivered as SaaS in the cloud
This is very interesting case indeed!
The solution provided by Steve is the first that came on my mind, but if this doesn't work you can try with media queries:
Hey Jordan, (I'd love a discussion here, but since this is technically not a Sitefinity styling problem, feel free to take it outside and use email which we've already exchanged earlier this week) Like I said to Steve in an email as well, there is unfortunately a difference between things that SHOULD and things that ARE happening when you're using media queries. From my experience as soon as you're using .class .class or .class #id statements in media queries you can expect strange and not cross-browser behavior, especially with Opera and FF v3. Vendor prefixes in a media query are also a guarantee to get your customers on the phone often. --- Try using ctrl + / ctrl - in different browsers on a responsive page. Where Firefox will ultimately kick in a max-width:320px, Chrome won't. Internet Explorer 9 will but (and I quote @TommyLee, a Microsoft IE evangelist) 'It will not trigger a media query in IE10' in a directly asked question. --- In this case a mediaquery kicks in setting the wrapper to a min-width of 1540px. Since my screen is 1680px wide, naturally scrollbars appear. (see screenshot mq_chrome.png). So technically everything works 100% as it should, but it's a major nusance... As Steve pointed out, you'd expect .sfPageEditor .sfWrapper width:960px; to work,and it does in 80%-90% of the cases, but I've managed to snapshot one of the cases where it didn't (see mq-firefox.png). Alternative could be to keep media queries out of the theme and into a seperate linked stylesheet and load that conditionally or something like that... need some time to figure out something bulletproof. Jochem.
The #wrapper can be placed inside your master page as a root element or if you don't want to use master pages you can set CSS class to the root layout element - .wrapper (in this case use .sfPageEditor .wrapper)
At any time when you can provide us an access to some dev instance of the website we can check the things directly there.