| Register | FAQ | Calendar | Search | Today's Posts | Mark Forums Read |
|
#21
| |||
| |||
| I have to point to one of 3 IFrames so you use the create style for a unique element Sorry, not sure I'm following you, but I'll give it my best shot. If you create a Class Style for each unique element with positioning, etc. then you can apply that style to each item as it's selected using the CSS Editor in GoLive. |
|
#22
| |||
| |||
| I haven't even tried using DW yet. I looked at it and remembered why I use GoLive. Here's hoping DW gets Adobefied. There is a lot to learn between Dreamweaver, CSS web standards, and scripting. I tend to jump between DW & GL. I've got crazy methods, but at least my methods allow me to get my work done while still getting a better handle on DW. I figure by the time I master DW and start to feel good about myself, Adobe will then make it like GoLive. 8-) |
|
#23
| |||
| |||
| Not to burst a bubble but Linda's 'position: fixed;' demonstration still does not hold the menu in place for MSIE6 users (which on my site logs makes up over 50% of visitors - that's a large audience to exclude). You can run into trouble if you are making visual design elements that do not flow with the menu. Her page is safe whether the menu stays in position or not - - since there is no content to jumble in the left and right sidebars. |
|
#24
| |||
| |||
| Hi Jim, I thought there could be some kind of a problem with my methods. Any suggestions on the best way to make it work right for Buko? Maybe Buko should post a link to a sample of his page when he gets far enough along so that others can help him fix any potential problems? Or is it a hopeless case using my methods? Thanks for posting. Linda |
|
#25
| |||
| |||
| What you are doing with the GoLive interface is the same thing that Nate mentioned with limitations on MSIE6. You are still working with the position: fixed; attribute - - just with GoLive's way of doing it. There are a few workarounds linked via post #8. However, if you look at the concept of a fixed menu as a feature and not a requirement, there is not much to worry about. What a designer needs to worry about is if their unique use of fixed positioning will prevent someone from making use of the site because the browser chokes on an unusual layout - - or if it just makes the design look wonky. Your example page looked fine either way. |
|
#26
| |||
| |||
| Thanks Jim! |
|
#27
| |||
| |||
| well if all that happens is that IE6 users don't have a stationary menu I can live with that. |
|
#28
| |||
| |||
| as an "out of the box" solution - why not simply have the central text in a div with the overflow set to scroll? that way the viewer could scroll the central text without touching the outer divs. or is this not sensible (I've done it on a couple of sites of mine - so tell me if it's a no no) |
|
#29
| |||
| |||
| > or is this not sensible (I've done it on a couple of sites of mine - so > tell me if it's a no no) I think it's a no no. Having the most important part of the page in a scrolling box *could* mean that you have to mess with 3/4 different scrollbars (depening on your browser viewport dimensions). In addition you have to grapple with the problem of printing the page. I avoid scrolling boxes like the plague (which is good to avoid!). -- Murray |
|
#30
| |||
| |||
| I agree with Murry |
![]() |
| Thread Tools | |
| Display Modes | |
In an effort to better serve ads to our visitors, cookies are used on objectmix.com. For more information, check out our Privacy Policy.