Width problems with select option in WebDialog

tt_su

Yes, the user's default browser has no connection to SketchUp's WebDialog. Currently we use the OS's built in framework which is IE under Windows and WebKit under OSX.

I'd recommend you look at the WebDialog Wiki I compiled if you haven't read it yet:
https://github.com/thomthom/sketchup-webdialogs-the-lost-manual/wiki/Doctype---Quirks-vs-Standard-vs-Superstandard

Btw, I just checked on my Win8 machine with IE11 and it's fixed:

This might just be an IE10 glitch. Annoying visually, but at least it's still fully functional.

jolran

 <option value='' disabled selected style='display;none;'>................Choose season.............</option>

Placeholder HACK
You will have to do some testing in JS to eliminate this selected.

tt_su

That's a very fragile hack... and one that adds a different visual noise - and extra code.
Since it's working as it is I would just leave it. Padding with dummy characters with a dummy list item won't ever be able to accurately adjust the length.

Aerilius

Let's better not use pixel sizes to dimension anything that will contain text.
Every box that contains text is better dimensioned with em.

jolran

Ok.... you liked that hack dident you....How bout this one..


<!DOCTYPE html>
		<html xmlns="http://www.w3.org/1999/xhtml">
		<head>
		<style>
			.DL_selection select {
				width;250px;
			}
			.op;after { content;"                                       ";}
		</style>
		<meta http-equiv="MSThemeCompatible" content="Yes">
		<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
		</head>

		<body>
			<div class="DL_selection">
			<select name="season_select" id="season_select">
				<option class="op" value="year" id="year_season_select" >year</option>
				<option class="op" value="summer" id="summer_season_select">summer</option>
				<option class="op" value="autumn" id="autumn_season_select">autumn</option>
				<option class="op" value="winter" id="winter_season_select">winter</option>
				<option class="op" value="spring" id="spring_season_select">spring</option>
			</select>
			</div>
			</body>
		</html>

@unknownuser said:

Padding with dummy characters with a dummy list item won't ever be able to accurately adjust the length.

Now since he is using style 250 px for the select element I naturally assumed he wanted that size. Spaces are acurate enough for that.. Wont work dynamically, has to be tested and nudged to liking, so in that sence not accurate..
Don't know the output from the select though. Pseudo element should not affect the value...

jolran

Even SVG text element ?

tt_su

hmm.... does an explicit 100% width also work?

Dan Rathbun

FYI using an inline STYLE attribute, kills the META "MSThemeCompatible" feature that is set in the HEAD section.

IE:
<select ***style="width:250px"*** name="season_select" id="season_select">
causes the select control to render like it is in old Windows 3.x.

The example above that shows using an inline stylesheet with a class to control width, is a much better way to go.

I think that inline STYLE attributes are considered obsolete now.

jolran

@unknownuser said:

FYI using an inline STYLE attribute, kills the META "MSThemeCompatible" feature that is set in the HEAD section.

Really ? Did not know that. Yet another reason to avoid inline styling.
Dumb question: Do you know if it kills the META just for that particular element or just by using inline style once in the document everything is ruined, if you understand my question.

I mainly use classes because it's easier to switch styling just by toggling class on/off..
It's difficult to overide that if using inline style or ID selectors.

maricanis

I would avoid any spaces based alignment, because GUI is translated in few languages, and with spaces I can't predict how long it will be in each language.

For styling classes are much better solution, but in example I just wanted to point out that I need some predefined width.

Thanks Dan, I didn't know that inline styles render controls differently than is style is defined in CSS class.
I'm also interested if it kills META for the whole document or just that one control.

Thom, I've just read your link Doctype---Quirks-vs-Standard-vs-Superstandard and it made me completely puzzled. When I include:
<meta http-equiv="X-UA-Compatible" content="IE=8"/>
it renders my GUI completely different then before, and all dialog alignments look crazy.
Must look little bit more into this rendering mode thing.

Is it conflicting in any way with meta tag Dan proposed in one post?
<meta http-equiv="MSThemeCompatible" content="Yes">

jolran

@unknownuser said:

I would avoid any spaces based alignment, because GUI is translated in few languages

Fine, then.

I would stick to IE=edge in the META. Or set specific version of IE.
I use D3.js and it wont launch otherwise since using CSS3 selectors/HTML5.. If you don't. Then you will have to include Sizzle or Html5 Shiv since any library dependent of CSS3 selectors need IE9(?) and up. For Mac don't know..

tt_su

@maricanis said:

Thom, I've just read your link Doctype---Quirks-vs-Standard-vs-Superstandard and it made me completely puzzled. When I include:
<meta http-equiv="X-UA-Compatible" content="IE=8"/>
it renders my GUI completely different then before, and all dialog alignments look crazy.
Must look little bit more into this rendering mode thing.

Are you familiar with the different document modes rendering engines use depending whether the HTML is valid or not? That specific section describes that the IE engine, when embedded is much more conservative and will keep on using an older document mode even if you have a newer IE engine installed. This differ from how the browser version of IE picks the render mode.

maricanis

@tt_su said:

Are you familiar with the different document modes rendering engines use depending whether the HTML is valid or not? That specific section describes that the IE engine, when embedded is much more conservative and will keep on using an older document mode even if you have a newer IE engine installed. This differ from how the browser version of IE picks the render mode.

Frankly, no experience and knowledge about document modes, I've just used the default ones till now.
Any suggested readings on this?
Especially related to embedded vs. browser mode?

Thanks again!

Dan Rathbun

@maricanis said:

I'm also interested if it kills META for the whole document or just that one control.

You guys might have to search the Microsoft websites for details.

I think changing certain style attributes of control elements will cancel the OS theme styling for that particular element. And then changing other attributes is OK.

You'll just need to experiment.

Some 3rd party wiki blogs seem to indicate that changing background and border at the document level might cancel the theme styling for the entire document, but I have never had a problem setting the WebDialog background color to match the system dialog background color, and still having controls rendered in the OS theme.

eneroth3

Another solution would be to stop using IE and use a real web browser for dialogs for a future SU version. Perhaps pack Gecko or something similar. This would also solve some of the the problems with web dialogs being platform dependent.

Dan Rathbun

Yes I agree, and have already "pushed" adding a GeckoDialog class to the API.

tt_su

@eneroth3 said:

Another solution would be to stop using IE and use a real web browser for dialogs for a future SU version. Perhaps pack Gecko or something similar. This would also solve some of the the problems with web dialogs being platform dependent.

Oh yes! We really want that. Unfortunately it's not that easy. Bloat is a big problem with these embedded browser frameworks. Then there is the technical support.

tt_su

@maricanis said:

Frankly, no experience and knowledge about document modes, I've just used the default ones till now.
Any suggested readings on this?
Especially related to embedded vs. browser mode?

I always make sure I use strict mode (full standard mode) and that mode renders best across different browsers and is the way forward. Everything else, quicks mode, is just legacy war damage from the ancient browser battles .