WebDialog help - hide scrollbars

Dan Rathbun

NewOne, and all ... I found this article on virtuosimedia very informative
Ultimate IE6 Cheatsheet: How To Fix 25+ Internet Explorer 6 Bugs

.. in addition the author recommends always using !DOCTYPE, and makes a good case.
.. other good tips, ie: the CSS Reset Rule.

have a read y'all !

chrisglasier

@newone said:

How can I hide scrollbars in webdialog?



css ...

body{
border;0px; 
margin;0px; 
overflow;hidden   }

Dan Rathbun

CSS Attribute overflow:

@unknownuser said:

With Internet Explorer 6 and later, when you use the !DOCTYPE declaration to specify standards-compliant mode, this property (overflow ) applies to the html object.
1. MSDN Library / CSS Reference: overflow Attribute | overflow Property

MartinRinehart

@dan rathbun said:

NewOne, and all ... I found this article ... very informative

Thanks, Dan.

So informative, in fact, that it would be nice if you posted a new topic re IE6 Cheat Sheet, or something similar so Google will find it for us.

chrisglasier

@chrisglasier said:

@newone said:

How can I hide scrollbars in webdialog?


> 
> css ...
> 
> body{
> border;0px; 
> margin;0px; 
> overflow;hidden   }
> 
>

Sorry forgot the pic
cgScenes no scroll.png

NewOne

@chrisglasier said:


> 
> css ...
> 
> body{
> border;0px; 
> margin;0px; 
> overflow;hidden   }
> 
>

But you don't use !DOCTYPE, right? Paste this on the top of your Html page and tell me if overflow works for you. Also your window border...

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">

chrisglasier

@newone said:

But you don't use !DOCTYPE, right? Paste this on the top of your Html page and tell me if overflow works for you. Also your window border...

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">

My top:



<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">

<html>

<!-- Copyright 2007-9 Chris Glasier -->

<!--This follows the Nameset format for easy integration-->

<head>

<title>Scene machine</title>

<LINK href="Scene machine.css" rel="stylesheet" type="text/css">

<script type = "text/javascript" src = "javascript/sceneDevice.js"></script>

</head>

Body css in external file of course.

chrisglasier

Adding "http://www.w3.org/TR/html4/loose.dtd" looks like this:

cgScenes no scroll 002.png

but the webdialog is on the local drive so I don't see the big deal. But please let me know if there is one!

NewOne

@chrisglasier said:

Adding "http://www.w3.org/TR/html4/loose.dtd" looks like this:

[attachment=0:1ma73d3a]cgScenes no scroll 002.png[/attachment:1ma73d3a]

but the webdialog is on the local drive so I don't see the big deal. But please let me know if there is one!

Same thing happens to me. So, I used your version of !DOCTYPE

Jim

Is there a single, simple answer to this?

NewOne

@jim said:

Is there a single, simple answer to this?

Well, I use <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> and <body scroll="no">. This seems to be working in all the cases. Other suggestions are not working if I use !DOCTYPE.

I think this is the universal answer.

thomthom

I use STRICT doctype and <body scroll="no">. Since this is for an application I don't care that it's not standard.

chrisglasier

@thomthom said:

I use STRICT doctype and <body scroll="no">. Since this is for an application I don't care that it's not standard.

Don't you think in good time such application may well need web connectivity, say, to get or set remote data? Making things comply with today's standards could save future hassles for following generations.

thomthom

I'm a strong proponent of webstandards. But I'm also pragmatic - this is to work around an SU bug where the scrollbar argument in SU's Webdialog class doesn't take effect.
It's not something that will cause problems for future plugins - if future SU corrects the bug, then this little attribute don't do much.

chrisglasier

@thomthom said:

I'm a strong proponent of webstandards. But I'm also pragmatic - this is to work around an SU bug where the scrollbar argument in SU's Webdialog class doesn't take effect.
It's not something that will cause problems for future plugins - if future SU corrects the bug, then this little attribute don't do much.

Ok no big deal except I am working on the API webdialog (which will include snippets). It seems there is a conflict between this:


body{
border;0px; 
margin;0px; 
overflow;hidden   }

and STRICT doctype, so shouldn't the solution be within HTML compliance and standards and not within Sketchup webdialogs?

It would be useful for me to understand.

Chris

thomthom

I don't know why the overflow with STRICT doctype within a Webdialog doesn't work - it's how you do it with websites.

@chrisglasier said:

so shouldn't the solution be within HTML compliance and standards and not within Sketchup webdialogs?

Seeing that the Webdialog has a scroll property for it's creating of the ruby class I'd expect that the scrollbars should be set from ruby. I think that the embedded IE control has a scroll property which developers who wish to embed HTML content can set to a fixed override. Why this argument isn't adhered to, I don't know.

I wonder if the SU dev team has been made aware of the scrollnar bug.
Was it so that this is PC only - that it works as expected on Mac?

chrisglasier

Thanks Thomas. BTW I think it therapeutic to use a STRICT doctype then abuse it by doing something non-standard - appeals to cynical Brits like me!

thomthom

@chrisglasier said:

Thanks Thomas. BTW I think it therapeutic to use a STRICT doctype then abuse it by doing something non-standard - appeals to cynical Brits like me!

It's make the standard conformant me twitch. x_X

thomthom

Ah!
There is a standard conformant way!

html
{
  overflow; hidden;
}

When removing scoll="no" and adding that to the CSS the scrollbars disappeared in STRICT mode.

Armed with that, you could sub-class the Webdialog class and tap into it's .new method and pass on the scroll argument to the webdialog when it's ready. Unless you're fine with just having it defined in the CSS and ignore the Ruby argument.
I was going to make a wrapper for myself, that took care of the matter where the size is only being read the first time it's created. At the moment, if you try to change the size arguments for a non-resizable webdialog they won't take effect unless you purge the saved settings.

chrisglasier

Good and noted! And used here.