ShadowMage

The broken search is a long standing issue. As mentioned, InvisionZone is the only one that can fix it. I believe the mods (specifically JSG) have contacted them, but they will not offer support because the mods do not own this forum account. The Refnes people own it, and they, unfortunately, don't seem to care. You can try contacting them yourself, but don't hold your breath.

Do you have a live link? If not, post your full code. You don't need to post each page. Just one (for example, your about us page) will do fine.

The :active psuedo class a:active { ... } targets an anchor element when it is active. In other words, while the mouse is pressed on the anchor (as dsonesuk pointed out). It has absolutely nothing to do with an active page (ie, indicating which page the user is currently on). Dsonesuk already gave you an example of how to use an .activePage class to target an anchor to highlight the current page: .activePage a { color: #C00;} Put that code in your CSS and add the activePage class to the appropriate links in each page, but only the link for the current page. In other words, in your About Us page, add the activePage class to the li wrapper for the aboutus.html link and only that link. In the Portfolio page, add it to only the link for portfolio.html and so on.

This has already been suggested and, more or less, shot down. It would offer some benefits, but not enough to make it worth the time and effort needed to set it up.

Yeah, I had been doing that. Apparently, somewhere along the line, though, something got goofed or didn't agree with something else and started a snowball.

If all your pages are separate files, the easiest way is to create a class and apply it to the appropriate link within each page. For example, in the About Us page you might have something like this: <li class='activePage'><a href="aboutus.html">About</a></li>|<li><a href="portfolio.html">Portfolio</a></li>|<li><a href="gfxgallery.html">GFXGallery</a></li>|<li><a href="gfxrequest.html">GFXRequest</a></li>|<li><a href="donate.html">Donate</a></li>

This whole thread is off-topic in relation to the purpose of this forum, but I'm interested because these pertain to my personal maintenance habits. I must ask, what do you mean by "doing otherwise"? I have always left my C: drive as my system drive and only my system drive. In other words, the only thing on that drive is my OS. All applications and data go on my F: drive. Does this fall under "doing otherwise"? If so, why is this a recipe for disaster? I have never had any issues. I never knew defragmentation was so hard on HDDs. I guess it makes sense though. Good thing I only do it once a month, if that. Probably more like twice a year. As for the pc cleaner, I certainly recommend CCleaner. We use it at work all the time and I've never had it delete anything it shouldn't. Even the registry cleaner does a really good job. Before making changes to the registry, it asks to back up changes (which I always do, though I've never needed to use one) so even if issues do pop up, you can restore all the changes that CCleaner made to the registry. I also use Windows' built-in cleaning tools as well.

If this is what you were referring to: the "files" I am talking about are the SVN properties of the actual files/folders in my working copy. There are only about 8 or 10 lines, so yes I'm sure that the whole file is identical. Anyway, think I'm going to make a hot copy of my repo in its current state and try to do the range revision merge and select either of the revisions of the "conflicted" file and see what happens. If my repo stays too broken, I'll restore it and then try JSG's suggestion to rebuild the branch from scratch. EDIT: The range merge seems to have done the trick. I think I'm going to have to rethink how I track my development and live versions (again) because I seem to have also broken the ability to merge the branch I've been using for development into the trunk... <_<This whole version control thing is incredibly handy (invaluable even) but it also appears to be incredibly fragile if you don't know what the heck you're doing.

Sounds like a hassle, but I guess I could give it a shot. It's a rather complex branch and there are quite a few changes. Better than leaving my repository in a broken state, though, I suppose...Thanks for the suggestion. Did you get a chance to read my edits on the OP? Does that change anything at all?

I am trying to reintegrate a feature branch back into the trunk, but I keep getting the following errors: Error: Reintegrate can only be used if revisions 107 through 185 were previously Error: merged from file:///C:/VersionControl/Repositories/SkyPrice/trunk to the Error: reintegrate source, but this is not the case: Error: branches/MarkupToggle/Forms Error: Missing ranges: /trunk/Forms:139,174 Error: branches/MarkupToggle/Scripts Error: Missing ranges: /trunk/Scripts:139,174,180 Error: branches/MarkupToggle/SkyPriceHome.php Error: Missing ranges: /trunk/SkyPriceHome.php:139 Error: branches/MarkupToggle/SkyPriceLayoutStyle.css Error: Missing ranges: /trunk/SkyPriceLayoutStyle.css:139,174 What do these errors mean and how can I resolve them so that I can reintegrate my branch? I am using TortoiseSVN. Thanks for your help. EDIT:I tried to do a revision range merge as well, but I get a conflict on the properties of one of my files. The conflict message is:Could not add property 'svn:mergeinfo' on 'SkyPriceHome.php' because it is already deleted. If I click the "Edit conflict" button, the editor shows up comparing the two property files, but there is absolutely no difference between the new one and the old one. So where's the conflict? Is it safe to just use one or the other and ignore the conflict?

Check your spelling on the handler. Also, I don't think this is correct: newNode=div.appendChild(newAddition);newNode.addEventListener("mouseover",function(event){cordinate(event);},false); I'm not sure what the value of newNode will be, but I can almost guarantee it isn't what you want it to be. Just get rid of newNode altogether and add the listener to newAddition like you did for the last two methods: newAddition.addEventListener("mouseover",function(event){cordinate(event);},false); Besides, you really don't need to append newAddition twice... (I left the spelling exactly as you had it, so you'll still have to find your typo... )

Could be a problem with FireBug. If the handler is called, then it is obviously a member of the new element.

Ternary operators can be nested just like if/else statements. When expanded, the ternary in the OP might look something like this: var val; // Start of the ternary syntax conversionif (window.Event) { //Condition from first ternary //"True" portion of first ternary val = e.pageY;} else { //"False" or "else" portion of first ternary val = event.clientY; if (document.documentElement.scrollTop) { //Condition from second ternary //"True" portion of second ternary val += document.documentElement.scrollTop; } else { //"False" or "else" portion of second ternary val += document.body.scrollTop; }}//End of the ternary syntax conversion document.getElementById('cursorY').value = val;

FWIW, the main problems with the code in post 24 are misplaced tags. For example, style, link, and meta tags must be in the head. You have an extra closing head tag. Content elements (such as p, h1-6, span, div, etc.) cannot be in the head and must be placed in the body. There's no closing form tag. Stuff like that.

Ok, well, the code in your second post at least looks valid so we'll use that if it does what you want (with the exception of the border). I'd recommend changing the doctype to at least transitional (though I strongly recommend strict). See here for a list of available doctypes. In the head, there is a <link> tag with a reference to a file named style.css. Do you have access to this file? If so, search the file to see if there is an entry for the body tag. It should look something like this:body {/* stuff here */} There may or may not be other tag names in front of it. If you can't find such an entry, add it. Once the entry is there, add the following between the { and } brackets:border: 5px solid #00FF00; If you do not have access to style.css you'll need to add an inline stylesheet. Somewhere between the <head> and </head> tags (but not inside any other tags) add the following:<style type='text/css'></style> Now between those two tags, add the entry I showed you above.

I recommend it, yes, but if you really want to try to fix up your current page I suppose I can try to work through it with you. Do you still have a copy of your original document? I think that one was better.

You still have some really funky stuff going on. There's no <head>, you have no opening <body>, the first <h1> has no opening tag, empty <script> elements, mismatched tags and attributes...As for the border CSS, this:div{Border:15px solid;Border-syle:double;border-radius:10px;border-color:#006600;}will make a border around all div elements, not your page. Ingolme's code targeted the body, as in:body{Border:15px solid;Border-syle:double;border-radius:10px;border-color:#006600;}Also, the <style> element has no opening tag. Seriously, though, I suggest reading the tutorial and starting over. EDIT: After rereading your code, I'm guessing that most of the errors mentioned above came from the "cleaning" that the validator did to your code. It's never really a good idea to let the validator clean your code for you, because it usually just messes it up worse than it was before. It's better to read through all the errors it shows you and fix them yourself. But even your original page had a ton of errors in it so I still recommend starting from scratch.

Post your new code so we can see what you got going on.

What you're looking for is the location object. If you want to maintain browsing history, use the assign() function. This will enable the user to hit the Back button to get back to the previous page. The replace() function replaces the current page in the history. For example, the user is on Page A. Then goes to Page B which has your button on it. The button takes the user to Page C. If assign() is used to get to Page C, hitting Back will take the user back to Page B. If replace() is used, it will take the user to Page A, since Page B was replaced in the history by Page C. I am not sure how modifying the href attribute handles history, but I would assume it would act like replace().

This is going to sound a bit blunt and harsh, but you have a lot of funky stuff going on in that code you posted. No problem. You're learning, I understand that. However, you might just want to take a step back and go through the HTML tutorial, start to finish, to see how HTML documents should be written. You have a lot of mismatched or misplaced tags. And as for the CSS code Ingolme showed you, it belongs between <style> tags.

But what happens when the div would normally need to be much smaller? If that 620px is small enough to fit in its parent but too big to fit in the space available? Or if it never reaches 620px but stays at, say, 500px? In such situations, it would overlap the MinorColumn. EDIT: Just tested it in FF (using the link from OP's latest attempt) and it does indeed overlap (well actually it goes behind) the MinorColumn.

That makes it 100% of its parent's width not 100% of available space. Would this not render the float useless and overlap the MinorColumn?

Or you could just use white-space: nowrap; on the original h2 to prevent text from wrapping to new lines when it doesn't fit.

As dsonesuk mentioned, my original suggestion was to move the HTML code for your MajorColumn div below the MinorColumn div and remove the float from the MajorColumn. AFAIK, this is the only way to get the MinorColumn to stick to the left and have the MajorColumn be elastic because if you float MajorColumn (as in the latest suggestion from dsonesuk), it will not fill all available space, but instead shrink to fit whatever content is inside it.

Hmmm...That should work. Try clearing your browser cache. If that still doesn't work, try adding !important to the inline style like this:style="margin-right: 0px !important;" Usually, I do it the other way around. I'll give the elements a left margin and use the :first-child psuedo element to remove the margin. The :first-child selector is supported in all major browsers (including all but the most ancient ones). a { margin-left: 15px; }a:first-child { margin-left: 0px; }