I just upgraded from CS5.5 to CS6 and have lost the ability to quickly insert the img hspace attribute.
I very often take advantage of the img hspace attribute. While I know it is deprecated, is still fully supported, and codewise, more efficient than an inline style. My problem is each image (and there are many) needs a different hspace so I can't just make a reusable class (which is what css excels at).
Using hspace="5" vs style="margin:5px 0" is much shorter and easier. Plus there is no way to add an inline style in the css panel. Dreamweaver keeps wanting to modify the class of the <a href> tag around the image instead of adding the code inline to the image itself. In CS5 I simply entered the desired number in a single box and I was done. Now customizing each and every image will take many times longer.
Please don't force me to code the way you choose. Let me choose when to stop using deprecated attributes. Is there an option that I haven't found to re-enable the hspace and vspace quick entry boxes in Dreamweaver CS6?
lkupersmith wrote:
While I know it is deprecated, is still fully supported, and codewise, more efficient than an inline style.
My problem is each image (and there are many) needs a different hspace so I can't just make a reusable class (which is what css excels at).
Using hspace="5" vs style="margin:5px 0" is much shorter and easier. Plus there is no way to add an inline style in the css panel.
Now customizing each and every image will take many times longer.
Please don't force me to code the way you choose.
So, as Nancy said hspace is deprecated and has been for quite a while. I am surprised anyone is still using this to be honest.
I am struggling to understand why you would need to change the hspace per image. Regardless of how it's coded, this is a lot of work when it would be easier to make everything consistent. Inline styles, although they will solve the hspace issue, are still not recommended as they require much more work in the long run.
As mentioned, I am at a loss at trying to understand why each image is individually coded. But, you could create several classes and then apply a different name to each image? This would at least cut down some of your coding.
.One{margin:0 5px;}
.Two{margin:0 10px;}
.Three{margin:0 15px;}
.Four{margin:0 20px;}
<img class="One" src="" alt="" />
<img class="Two" src="" alt="" />
<img class="Three" src="" alt="" />
<img class="Four" src="" alt="" />
Sorry I've taken so long to respond - I've got a lot going on today.
As I said originally, I know that these attributes are depricated but I think it should be my choice, not Adobe's, whether or not I continue to use code that is supported by every browser out there. This is something that was already in the program and if a user doesn't want to use it, they don't have to. But why remove it? It didn't really clutter up the properties panel.
As to why I still use hspace, I have pages loaded with columns and rows of images of glass art. I like using hspace to easily and quickly modify the spread between different size objects. So if an object is smaller, it will have a larger hspace. And before you recommend using sized cells or divs, I need variable cell sizes, but also need enough space around the image that the text in the row below won't wrap.
Here's a sample page to help visualize what I'm doing...
http://www.artglassusa.com/pages/ogrady_marbles.html
Depending on the page, artist, style of work, the hspace can vary from 2 to 20px or more. Sure I can make up a lot of classes, but I don't see a way to insert multiple classes into an object other than manually typing it in code view. Most of my images will already have a class "imgover" and will now need a second class for the spacing. Am I missing something in not seeing a shortcut for this?
From what I gather, CS6 allows you to insert multiple classes on objects. See: http://forums.adobe.com/message/4406523
I see there being 2 relatively simple workarounds if you want different size margins around each image.
Thanks, but inserting multiple classes in CS6 doesn't seem any faster than manually coding it so I'll skip that for now. If I were able to apply multiple classes quickly (such as control-selecting them from the class dropdown) your example of using many different classes would work OK. Adding the white space in Photoshop doesn't work as I don't always know what space I'll need as I'm editing dozens of photos.
At this point I'm going back to Dreamweaver 5 from the CS5.5 suite. It just doesn't make any sense for me to edit a perfectly working 320 page website because Dreamweaver 6 limits my options. I expect a tool like Dreamweaver to offer options, and not try to be the sole arbiter of when it's time to stop using popular attributes. There's a reason why new browsers haven't dropped support for these 'depricated' attributes. Everyone's suggestions are fine workarounds for a problem that in my opinion just shouldn't exist.
I completely agree with Lkupersmith! I have so many websites that have been up for years that are too tough to bring up to "standards" and I think it should be our choice to use deprecated code if that's what our work demands for the fastest solution until I can get them up to code. I had this issue with the ALT tag nag screen in Dreamweaver that was driving me crazy. Why nag me about the ALT tag only, why not nag me about using the <b> tag? It was like I was speaking another language to the Adobe moderator who insisted the ALT tag was required. Oy, such arrogance. And what about this sentence from an earlier post - "I'm so surprised people are still using this"... REALLY?? - is your world view that small?
markhuss wrote:
And what about this sentence from an earlier post - "I'm so surprised people are still using this"... REALLY?? - is your world view that small?
Apparently so.
I haven't used hspace or seen hspace used in website code for years. I thought everyone used margins and padding.
The interface of DW always gets progressively cleaned up and modernized with every upgrade.
Others have cried foul in previous years about the disappearance of, or new workflow for, their deprecated pet interface items too. This year, CS6's - probably overdue - cleanup included hspace.
It was like I was speaking another language to the Adobe moderator who insisted the ALT tag was required. Oy, such arrogance.
Oy vey! If ALT attributes offend you, consider vision impaired site users who can't "see" images. What will they do? I think the arrogance is on your part.
Why nag me about the ALT tag only, why not nag me about using the <b> tag?
Because bold text is not necessary for web accessibility. ALT attributes are.
And what about this sentence from an earlier post - "I'm so surprised people are still using this"... REALLY?? - is your world view that small?
Sorry but sticking to old school ways because some browsers still support them isn't responsible web design. Water seeps to its own level. Your ignorance about web design will soon surface (if it hasn't already). People who might have been interested in you/your services will no longer be because you're so out of touch with modern web standards.
Best of luck,
Nancy O.
Anita Adamski wrote:
THANKS ANDY for actually answering the question, post 13, I was looking for V Space too.
Amazing how rude people can get --- when they don't know enough to answer the question they decide the person asking is somehow stupid or inept.
Post #13 isn't correct at all but people here were just too polite to point it out. If you want the correct answer then please start a new thread. HSpace and VSpace isn't available in DW CS6 but you can still manage to get exactly that effect (and sometimes better results) using CSS. Please start a new thread if you want to know the correct answer.
Good luck.
I used Post 13's directions yeterday and it works fine inside DW CS6 and tests perfectly in all browsers I ran it through. What part isn't working for you? CSS is not the way to go for this particular solution, although if it always is on your projects that's wonderful. We're all happy now, thank you Dreamweaver.
I used Post 13's directions yeterday and it works fine inside DW CS6 and tests perfectly in all browsers I ran it through. What part isn't working for you?
Use the W3C validation tool to check your code.
H-space and V-space are deprecated (obsolete) and have been since HTML 4.
CSS is not the way to go for this particular solution,
It is if you don't want errors in your HTML. ![]()
Nancy O.
hspace and vspace do not show up as errors in the W3C scan (with DocType HTML 4.01 Transitional). I've still got pages I haven't converted and just did a test with the online scaner. I get:
when checking all of my pages.
If you're using a later DocType, then maybe yoou'll see errors.
WOW. The topic/question is H-Space support in DW CS6. Deprecated tags isn't the issue, nor is how you write code.
And, by the way, many websites are using deprecated tags, which is why ALL browsers will continue to fully support (without error) V- and H-Space deprecated tags for the forseeable future. I just used V-Space very successfully on my ---- wait for it ---- HTML5-based fluid grid responsive website. Thank you Dreamweaver CS6 for getting it right and leaving the tags in.
North America
Europe, Middle East and Africa
Asia Pacific