ShadowMage
-
Posts
3,476 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by ShadowMage
-
Do you have a live link to a test page where we can see the issue ourselves?
-
Nothing directly, anyway. You have to contact the forum admins, which has been done several times and unfortunately, the admins don't seem to care or they aren't active enough to have seen the multiple posts/reports on the issue.
-
The code you have to change the cursor should work. I'm a little confused as to why you have <a> tags directly following the <style> tag. Do you have the <style> tag in the body? It should be in the head.
-
Remove the float from the major column and move it (in your code) so it is below the minor column.
-
<a href="http://world.honda.com/HRC/" target="_blank"><img_id2 src="pictures/logo/hrc.png" alt="HRC"/></a> Use the id attribute to give an img (or any other element) an id. The tag names never change. EDIT:If you were basing your attempt on the example in my previous post:#image_id { ... } The '#' is the CSS id selector and 'image_id' would be the id to select. That selector would select the element with an id equal to 'image_id'. You would replace 'image_id' with whatever id you want to give your image as long as the id in the CSS selector matches the id on the element you want to select.
-
If I understand correctly, you need to remove the margin from the last link in your list. Give it an id or use inline styling and set the right margin to 0. You could also use the :last-child psuedo-class but that's CSS 3 and won't be supported by older browsers.
-
You can either give the image an id and target it in CSS that way or you can target it using the general descendant selector from the h4: #image_id { ... } h4 img { ... } Be aware that the first one is specific to a single img element, while the second will target all img elements that are descendants of h4 elements. Since you say you have a lot of different image sizes, you're probably going to want the first. You may also be able to just use inline styling:<img ... style='width: 70%;' />though you'll be compromising a bit of maintainability by doing so.
-
Just width:width: 70%;
-
Apparently HTML 5 removes the ability to specify values for the width/height attribute in percentages. You can just define those with CSS or specify the value in pixels. Personally, I'd move it to CSS.
-
You have JavaScript which creates a <marquee> element, not a JavaScript powered marquee. The marquee element is deprecated and should not be used. You can use JavaScript to create a marquee using standard elements (like a div or span). Something like this:http://blog.wardelld...script-marquee/ Give it the HTML 5 doctype instead of the strict XHTML doctype. The HTML 5 doctype looks like this:<!DOCTYPE html> EDIT:You could also use CSS 3 transitions and animations to create a marquee, but you'll sacrifice compatibility since older browsers (most notably IE 8 and below) do not support them.
-
As Ingolme mentioned, the target attribute is deprecated in (X)HTML strict. You can either use a transitional or HTML 5 doctype. As for the marquee, you'll need to use JavaScript to animate the left/right or margin properties of the element. Google should be able to help you find some examples or tutorials.
-
What is the error message the validator is giving? Which line is 62?
-
You could use jQuery's :focus selector and then check the tag name: if (($(':focus').attr('tagName') == 'textarea') || ($(':focus').attr('tagName') == 'input')) { //do something}
-
A simple "Thank you" is usually sufficient.
-
For maximum compatibility, gradients are typically done with small images that are 1px wide (or tall depending on the orientation of the gradient) and then repeated horizontally (or vertically, again depending on the orientation).
-
You have two options. Which one to use depends on how much browser compatibility you want. One:Use CSS 3 animations/transitions.This will limit your compatibility to newer browsers. For example, IE 8 and below do not support animations and transitions. There's an excellent demo/tutorial here that will show you how to use much of the new CSS 3:http://css3.bradshawenterprises.com/ Two:Use JavaScript.This will give you maximal compatibility since all but the most ancient of browsers support it. I don't know of tutorials or references off hand but you might be able to Google something like "animate image position with javascript" and find some tutorials. jQuery makes animations incredibly easy so maybe you want to try to find a jQuery tutorial.
-
You set x to the element with id "OTWOpt1" here:var x = document.getElementById("OTWOpt1"); but then try to access it as OTWOpt1 here:var y = OTWOpt1.options[x.selectedIndex].value; The variable OTWOpt1 does not exist. Your browser's error console would have told you this if you had checked it.You should be using x:var y = x.options[x.selectedIndex].value; There are a few other places where you use OTWOpt1 instead of x as well.
-
As long as you have the file type drop set to "All files" as Boen pointed out. Otherwise, you'll get a file named "welcome.html.txt"
-
Can't tell you the number of times this has been suggested and shot down...It's a great idea, but the owners won't go for it (quite likely for the reasons Ingolme mentions).
-
They specify the corresponding min/max values. For example, min-width: 200px will not allow the element to go smaller than 200px wide. The effects of these properties aren't easily noticeable (especially the min- properties) until you resize the browser window. The max- values prevent elements from getting too big. So if you set a max-height and you put a lot of content in an element, the element will only be as tall as its max-height will allow. Content that doesn't fit will be displayed (or hidden) depending on the overflow property. Usually, that means the element will become scrollable.
-
Like niche said, use float. Put all the images in a container with a set height/width and overflow set to auto and float the images left (or right, doesn't really matter). Well, actually, it can be done but it involves creating "click zones" using an image map, which is obviously more complex than the above method.
-
I'm not sure what you mean by changing its orientation to landscape (IMO all buttons are "landscape"), but you can modify its height and width properties to make it look how you want.
-
What browser are you using? Do you have a Doctype declared? The id should theoretically work with any element, but try moving the id to the h2 and removing the a.Or try changing it from id to name on the a element. Either way should work (though, the first is recommended since the name attribute is deprecated).
-
An ID is a unique identifier for a particular element, similar to the way that a Social Security Number or a driver's license number are unique identifiers for an individual. An element's ID can be used to set specific and unique styles for that element. Probably the most common use for an ID, however, is getting a reference to that object in JavaScript. There are a multitude of examples of this. Say you want to toggle the visibility of an element, such as a tooltip. Or append text to a specific element. Or get the text/value of a specific element or input. Another good reason to keep them unique is that the W3C says in the spec that IDs should be unique. These two questions are closely related, so I'll answer them together. The simplest answer is this: maintainability.Imagine trying to search through 5k lines of HTML to find one element that needs its style tweaked. That's rather large scale, but even 500 lines would be challenging. If you give that element an id and put its styles in a stylesheet (embedded or external), it's much easier to find. You just look for its ID. If you don't know it's ID, there are a number of tools for each browser you can use to find it (such as FireBug or DOMInspector for FireFox, or Chrome's Developer Tools). Again, the other answer is that the W3C recommends it to maintain a separation of content (HTML), style (CSS), and behavior (JavaScript).
-
Yep. I get that. I'm more worried about people overwriting changes that have already been made, though. Not two people trying to write at the same time. Since this is all form based, if Fred and Rita open the same quote at the same time, they'll both have identical data. Fred changes field A and saves. Rita now changes field B and saves. Rita just overwrote the change Fred made to field A because the form she has loaded still has the original data from before Fred's save. Currently, it isn't a big issue, but it's something I've been thinking about. We don't have very many estimators at the moment, but that may change. And obviously, that could make this a bigger issue.So the manual locking is currently the only option then? If automating it when they navigate to another page will prevent the use of multiple windows, I can't do that because that is something they're currently doing.
