Why are browsers so picky?

Woo! And there might be more :slight_smile: What if I “keep the old and trash the new”?

Jokes aside. What do you mean by:

Now seriously, the slider has been working ok as far as I know. Your link to the latest version would concern just that little portion of code about function fitMenu (which works even without that link) and yes, all the other jquery staff if it wasn’t for the conflict. What use would it have having a up to date jQuery and half site still unresponsive?

As I discovered, the jQuery code and the slider code are both older versions. If you are happy with the way the site is working, there is no need to change anything. If you want to make any changes that might require more modern jQuery, this would be as good a time as any to update to a more modern version of jQuery. There is clearly a significant difference between the 1.7 and 1.11. You won’t know if the update process would be difficult or not until you give it a try. Replacing your older jQ with a newer version is easy enough. Replacing the older Camera jQ and associated files seems like it would be easy. But there are other JS scripts running on the page, too. Don’t know how those might be affected. If pure JS, they shouldn’t be. If jQuery, they might be. It’s up to you. Do you feel daring? What are your ambitions for the web site? The current version of the slider is responsive. How do you envision your site behaving as responsive?

BTW - the site looks like it was created with the aid of Dreamweaver. If so, please remember that Dreamweaver’s code is at least a decade old. As part of an update, I’d recommend replacing the XHTML transitional doctype with a modern <!doctype html>

Another BTW - if you want to eliminate the inner scroll bars, it will require some major graphics redesign. Are you willing to do that?

EDIT: In fact, “responsive” or even “fluid” will require even more serious graphics redesign. Are you willing to do that?

Yes, I will be willing. Those things require time mostly. And I would update if not for another thing I noticed when I delete the new jQuery call:

with it on instead:

I try increasing the padding but it looks like 30px is the full scale. They are too cramped.

Is there any way to make the slide work along with the new call? (I don’t think so :smiley:)
OK :pensive: replacing the compressed new version in jquery.min.js seems easy enough…but then I’ve still got jquery.mobile.customized.min.js and jquery.easing.v1.3.js what to do with them?

Those files are part of the slider system, as I understand it. When you replace the slider, Camera1, those files should probably be updated, too.
Go to the Camera site and check out the “Usage” section. It talks about those files.

The version available for download in the website is the one I have on. I don’t believe there are further updates.
It would be enough for me to solve the poblem with the padding.

Are you saying you have updated the Camera1 slider scripts?

There should be no problems with the padding since the padding is set by fitMenu.js.

You should be using menu6a.css and bubble6a.js.

I assume you are using a different site for your tests. Can you post a link to the test site?

I downloaded the .zip from pixedelic.com with everything in and checked the scripts versions. They are the same as those I have on.

Unfortunately not. I did a backup though.

I have disabled all the calls regarding the slider on pages that are not using it

<!--script type="text/javascript" src="https://code.jquery.com/jquery-latest.min.js"></script--> is commented out in all pages.

Pages having <script src="scripts/jquery-1.7.2.min.js"></script> (for lightbox) make the menu’s padding works as if the latest version, ergo as if the above mentioned call hadn’t been commented out.

There is another working page in your dropbox. Copy the folder to your PC. Double-click ilcontadinobio20150216.htm and see if the menu and slider work properly in your browser/s. They should.

Please note that I copied the HTML from your web site this evening and reformatted it… indented the stew out of it so I could find a couple of misplaced tags. The code is current. Please use the indented HTML on your site. It’s easier to troubleshoot when tags go missing.

In the process of indenting the HTML, I managed to clear most of your validation flags. From 70 down to 10. There were 2 mismatched tags. There is one ID that still needs to be fixed… IDs cannot begin with digits. Most or all of the other errors are unrecognized attributes that cannot be fixed. Don’t be too satisfied with this apparent improvement, though. If you change the doctype from a transitional to a modern <!doctype html>, you’ll see the error count go through the roof. You have many more deprecated attributes that should be replaced by CSS. (Yaaaay, Dreamweaver.)

I found jQuery 1.7.1 on my PC, so that’s what is in this file. You can update it to 1.7.2 if you wish. Ideally, it should be 1.11.x, of course.

The problem with using the latest jQuery is that the Camera code is not quite up to date. I recommend finding a way to bring it up to date. You might find the answer on the Camera web site (they have a small forum), or maybe the author would be interested in updating his code again. Wouldn’t hurt to ask.

https://www.dropbox.com/sh/uos2098ouse28re/AADmCH_oSlPreBqjm2cPMW8Wa?dl=0

It doed :smile:

And then I guess on all pages.

Should be but it cannot 'cause it wouldn’t work.
Yes, the author had stopped the upps even before I used it.

I’d rather do it as well seen I have to revising everything.

I can’t remember where they come from anymore :slight_smile:

What would you suggest a modern doctype declaration be?

He gave it already :wink: .

You are right. I didn’t know that was HTML5 statement untill 5 min ago. Good! :slight_smile:

Which post are you referring to?

Is there any chance to eliminate that initial bug in the bubble positioning?

I believe the bubble was slightly tinner before. Is it possible to reduse its thickness so that it can fit that darker green part that is supposed to be the background not rounded part?

What initial bug? Better to spell it out so we don’t misunderstand.

The height of the bubble can be changed, but would you please attach a screen shot showing how it looks now? I thought the height of the bubble was fairly short. As such, I don’t understand what you are describing.

Going with an usupported slider was not too clever.

I’d like to recommend that you begin searching for another slider… something that is being supported. I don’t use 'em so I have no recommendations. Paul likes the bxslider http://bxslider.com/ and the Anything Slider http://css-tricks.com/examples/AnythingSlider/#&panel1-1. Those would probably be good places to start.

If you are unwilling to leave your current slider, then you need to find a jQuery person who is willing to find the outdated code in the current camera.js and change it to modern jQuery language. The errors show up in the console window, so it doesn’t appear that it would be impossibly difficult, just time consuming for an experienced coder. Best bet, though, is a current slider.

Sorry, the editing window timed out before I thought about this.

Maybe this is what you want. Height and margin-top are changed. Just guessing:

bubble6a.css

#sses2 li.highlight {
    background:url("../images/mb2_2.gif") no-repeat scroll center center #693500;
    border-radius:0.75em;
    height:1.25em;
    margin-top:-0.625em;
    position:absolute;
    top:50%;
    z-index:1;
}

It is online. You will spot it right away, just click on some item that is not the home and distance the cursor from it. (The bubble fails in positioning itself on the chosen item.)

Bingo! Thank you.

I built the website almost for fun. I still can’t believe I managed to put it online.

I will have a look at your suggestion and even send a mail to the author of my current slider.

The bubble has to move to position itself properly.

In bubble6a.js, try uncommenting both of these lines and see if that makes a difference: (stab in the dark)

if (k > -1) {
    slip.style.width = items[k].offsetWidth + "px";
    slip.style.left = items[k].offsetLeft + "px";  //uncommented seems to eliminate initial annoying annimation.
    sse2.move(items[k]); //comment out this line and uncomment the line above to disable initial animation
}

I think I fumbled my English a couple of posts ago.

I meant to say “a currently supported slider” as opposed to the slider that you are currently using, but expressed myself too briefly. Sorry if this caused any confusion.

Hope you get some feedback from the author or his web site.

Doing thet the bubble disappears altogether (it showes up only when the cursor meets its operational area). By its look it seems that the bubble sort of lack time to settle itself on the item.

Yes, I guessed with “current” you meant a supported one as well.

Well, I don’t think I will get any from him.

Please substitiue (replace) these files in the working page that I sent for their similarly named counterparts.

<script type='text/javascript' src='scripts/jquery-1.11.2.js'></script>
<script type='text/javascript' src='scripts/jquery.mobile-1.3.0.min.js'></script>
<script type='text/javascript' src='scripts/camera133v2b.js'></script>

Please use the inconveniently long filename, version number and all. It’s nice to be able to tell what’s being used while developing a page.

jquery-1.11.2.js (277.5 KB)

jquery.mobile-1.3.0.min.js (141.1 KB)

camera133v2b.js (67.6 KB)