 Bleepbleepbleeping Computer Bleep Bleep, Or how do you account for varying browser settings |
Welcome Guest ( Log In | Click here to Register a free account now! )
Register a free account to unlock additional features at BleepingComputer.com
Welcome to Bleeping Computer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.  |
  Apr 11 2008, 10:41 AM
Post
#1
|
|
|
Member  Group: Members Posts: 24 Joined: 8-April 08 Member No.: 201,680  |
My code is pretty tidy and I'm now using divs, ids or classes and an external stylesheet for almost every element following some pointers from the folks at Bleeping Computer, but no matter whether I use absolute or relative position, px, pt, or any other combo of values it all goes to pieces the second I change the screen settings. Is there a simple way around this or do I just build it and tell people to adjust their diplay (I really don't want to do this and am prepared to put the work in not to, but I'm a newb and running out of ideas) Any pointers appreciated. cheers Jason |
 |
 
|
|
Apr 11 2008, 11:31 AM
Post
#2
|
|
 Hail Groovicus! Group: Site Admin Posts: 5,673 Joined: 5-June 04 From: Vermillion, SD Member No.: 689 |
What happens when one changes resolution? If you wanted to, I suppose you could code a page for each resolution, but that would be a huge PITA, especially considering how many resolutions are possible (there are 13 possible on my system). Do you really want to code that many variations?
-------------------- |
|
|
|
|
Apr 11 2008, 12:03 PM
Post
#3
|
|
|
Member Group: Members Posts: 24 Joined: 8-April 08 Member No.: 201,680 |
What happens is that everything becomes completely disorganised (images and hr's move relative to width etc etc) and it looks like a chimp has randomly placed objects on-screen.
I'm just concerned that if I don't do something the chances of anyone spending more than a second looking at it (assuming they don't have the same settings as I do) will be nill, making the whole enterprise a bit of a waste. There must be a way around it (unless I'm completely misunderstanding the way this works) as most sites you visit, even basic ones, render as you might expect when you visit them and don't assume a given resolution presumably. |
|
|
|
|
Apr 11 2008, 12:55 PM
Post
#4
|
|
|
Hail Groovicus! Group: Site Admin Posts: 5,673 Joined: 5-June 04 From: Vermillion, SD Member No.: 689 |
QUOTE but no matter whether I use absolute or relative position, px, pt, Have you tried using percentages? I don't know what to tell you. I always code my pages for 800x600 so I don't have to worry about scaling down. Maybe you want to rethink your layout? -------------------- |
|
|
|
 Apr 11 2008, 04:51 PM
Post
#5
|
|
|
Member Group: Members Posts: 24 Joined: 8-April 08 Member No.: 201,680 |
Well, dont I feel like an idiot....
I took your advice and went through my code with a fine tooth-comb looking to rewrite it. Found a missing closure that had thrown the entire image positioning out of whack somehow. Lesson learned. If in doubt, walk away and come back an hour later ready to concentrate. Cheers Jason |
|
|
|
|
Apr 14 2008, 06:54 PM
Post
#6
|
|
|
Member Group: Members Posts: 17 Joined: 8-April 08 Member No.: 201,755 |
You could consider validating your code as you build a page at various stages. One way that many professional designers use is to preview in Firefox with a Validating plugin. I favour "HTML Validtaor" the one that incorporates HTML Tidy. This will highlight any code errors each time you preview a page as it progresses. I find it saves a massive amount of time and agravation.
-------------------- >>>piskie<<<
|
|
|
|
|
Apr 15 2008, 02:05 PM
Post
#7
|
|
|
Member Group: Members Posts: 24 Joined: 8-April 08 Member No.: 201,680 |
Hey Pislkie,
Thanks for the pointers. I think.... Just ran my code past the w3 validator and it really didn't like it, despite the fact I'm coding from 2 reference manuals for HTML and CSS. Most common error was "omitted tag minimization parameter can be omitted only if OMITTAG NO is specified." which appear all over the place. I have no idea what that means, yet. Interestingly though, the Firefox error console only indicated 4 errors, which I was quite pleased about initially. Back to the drawing board. … Just for reference the above error is a DTD error! Thats why it's so common. Should be easy to fix if anyone else comes across it - Check your DTD and make sure it's done in full, including charset definition. This post has been edited by webrat: Apr 15 2008, 02:16 PM |
|
|
|
|
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:
| Lo-Fi Version | Time is now: 6th July 2008 - 08:14 AM |
© 2003-2008 All Rights Reserved Bleeping Computer LLC.