Hi all this is a carousel 2 v.0.1.10 with the frame borders set to outside in an inline construction. It works as expected in safari and chrome but breaks in firefox does anyone have any ideas?
Simon
http://www.bubblebubblebreath.co.uk/carousel/index.html
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Honestly I can’t tell you why for sure, I can only guess (uahhh):
It has to do with the white border and to which item it’s applied. It seems (but I can’t proof, that the white border is applied to an item in #item3 which is causing some troubles.
Assumed we call #item2 carousel-wrapper, then #item3 would be the carousel-content. So I would apply all styles to carousel-content (shadow, border…). In there, there is the carousel-pane1 which needs no styling at all. This (or far to this) is my preferred construction method which worked lower V6.
Another point:
Any reason for a left margin (35px) on #item1? I think this is pushing the carousel out of centered.
But as I already mentioned: a shot in the dark.
Cheers
Thomas
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Hi Thomas thanks for that I’ll give that a try.
the odd margin appears 'cause it’s cut and pasted out of the original document.
Cheers
Simon
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Thanks T that’s fixed it!
Question though that method doesn’t require the use of the “Move pane borders to outside” check box in carousel 2, so is that functionality broken in FF, or have I wrongly understood/applied it?
S
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Hi Simon,
the naked truth?
I haven’t played with c2 yet, so I do not know what that lil’ check is doing (or not 
so this is more dedicated to Walter.
All I know is:
The more purist the construction, the higher the chance for trouble-shooting. This sounds annoying but is T’s webdesign rule #1:
Cheers
Thomas
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Let me second this. Browsers are designed to put up with endless amounts of malformed HTML. They are pretty well defined by this ability. JavaScript is less forgiving, as in not forgiving at all. Any time you try to shift things around the page by removing them from one place and inserting them somewhere else, you rely on starting with a completely valid page, because otherwise, you really can’t know what you will get.
Walter
On Feb 28, 2013, at 8:35 AM, Thomas Kimmich wrote:
The more purist the construction, the higher the chance for trouble-shooting.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Hi Walter,
Are you saying that you need to see the original page to diagnose the fault?
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Please excuse my interruption, but what exactly does it mean when you say, “frame borders set to outside in an inline construction”? I think I recall seeing that as an option in Carousel 2, but I don’t know what it means.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
When you set up a carousel with Carousel 2, you may have added CSS borders to each of your panes. When the carousel effect is assembled, what you will see is those borders being clipped off by the surrounding “frame” element that defines the effect area during most of the animation. You see the left border clipped off, then the left border of the next pane appears at the right, and finally settles at the left again when each wipe of the animation finishes.
What this new option in C2 does is strips off the border from all of the panes, and moves it to the outside of the frame element. That makes the border stand still while the content wipes from right to left inside it. It’s not needed for all designs, but for some, it can make the effect look more finished.
Walter
On Feb 28, 2013, at 1:27 PM, RavenManiac wrote:
Please excuse my interruption, but what exactly does it mean when you say, “frame borders set to outside in an inline construction”? I think I recall seeing that as an option in Carousel 2, but I don’t know what it means.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
No, just that to begin with, your page must validate to go any further. Try this – leaving all of the panes on the pasteboard or page, remove all instances of the Action – all the tabs, buttons, panes and carousels. Publish the page somewhere, and go to http://validator.w3.org and paste in the URL of your published page. See if it validates. If it doesn’t, then fix what isn’t right. (Freeway will only ever generate valid pages all by itself, but Actions and anything you add through the various Markup options can definitely wreck its perfect record.
Carousel 2 adds some attributes to the page that are only valid in HTML5 – I still haven’t figured out how to replicate these in lower DOCTYPEs – which is why I asked you to remove the Actions from your page before validating the basic layout. The invalidities it adds to the page are NOT the type that would affect things in JavaScript, though. The things that really matter there are duplicate IDs or improperly-nested content.
Walter
On Feb 28, 2013, at 10:56 AM, Simon K wrote:
Hi Walter,
Are you saying that you need to see the original page to diagnose the fault?
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Hi Walt, i haven’t done this yet but my carousel in the original link was built fresh on a blank page in a new file and it still fails in FF
Simon
On 28 Feb 2013, 5:57 pm, waltd wrote:
No, just that to begin with, your page must validate to go any further. Try this – leaving all of the panes on the pasteboard or page, remove all instances of the Action – all the tabs, buttons, panes and carousels. Publish the page somewhere, and go to http://validator.w3.org and paste in the URL of your published page. See if it validates. If it doesn’t, then fix what isn’t right. (Freeway will only ever generate valid pages all by itself, but Actions and anything you add through the various Markup options can definitely wreck its perfect record.
Carousel 2 adds some attributes to the page that are only valid in HTML5 – I still haven’t figured out how to replicate these in lower DOCTYPEs – which is why I asked you to remove the Actions from your page before validating the basic layout. The invalidities it adds to the page are NOT the type that would affect things in JavaScript, though. The things that really matter there are duplicate IDs or improperly-nested content.
Walter
On Feb 28, 2013, at 10:56 AM, Simon K wrote:
Hi Walter,
Are you saying that you need to see the original page to diagnose the fault?
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
You have indeed found a bug. Sorry to have doubted you. Moving borders to the outside appears to fail in Firefox. It seems to be a timing issue. The border move is happening after the command to hide the borders on all the panes, when it doesn’t work that way in Safari. Very strange.
Further experimentation has shown that Firefox is not letting me copy the border style from one element to another because it is not reporting the combined border attribute as having any value. Check out the raw data:
| name | value |
|---|---|
| border | |
| borderBottom | |
| borderBottomColor | rgb(0, 0, 0) |
| MozBorderBottomColors | none |
| borderBottomStyle | solid |
| borderBottomWidth | 10px |
| borderCollapse | separate |
| borderColor | |
| MozBorderEnd | |
| MozBorderEndColor | |
| MozBorderEndStyle | |
| MozBorderEndWidth | |
| borderImage | |
| borderImageSource | none |
| borderImageSlice | 100% 100% 100% 100% |
| borderImageWidth | 1 1 1 1 |
| borderImageOutset | 0 0 0 0 |
| borderImageRepeat | stretch stretch |
| borderLeft | |
| borderLeftColor | rgb(0, 0, 0) |
| MozBorderLeftColors | none |
| borderLeftStyle | solid |
| borderLeftWidth | 10px |
| borderRight | |
| borderRightColor | rgb(0, 0, 0) |
| MozBorderRightColors | none |
| borderRightStyle | solid |
| borderRightWidth | 10px |
| borderSpacing | 0px 0px |
| MozBorderStart | |
| MozBorderStartColor | |
| MozBorderStartStyle | |
| MozBorderStartWidth | |
| borderStyle | |
| borderTop | |
| borderTopColor | rgb(0, 0, 0) |
| MozBorderTopColors | none |
| borderTopStyle | solid |
| borderTopWidth | 10px |
| borderWidth |
Note how most of these border attributes appear empty to JavaScript, except for the ones that are completely decomposed (border-left-color, for example).
Walter
On Feb 28, 2013, at 2:02 PM, Simon K wrote:
Hi Walt, i haven’t done this yet but my carousel in the original link was built fresh on a blank page in a new file and it still fails in FF
Simon
On 28 Feb 2013, 5:57 pm, waltd wrote:
No, just that to begin with, your page must validate to go any further. Try this – leaving all of the panes on the pasteboard or page, remove all instances of the Action – all the tabs, buttons, panes and carousels. Publish the page somewhere, and go to http://validator.w3.org and paste in the URL of your published page. See if it validates. If it doesn’t, then fix what isn’t right. (Freeway will only ever generate valid pages all by itself, but Actions and anything you add through the various Markup options can definitely wreck its perfect record.
Carousel 2 adds some attributes to the page that are only valid in HTML5 – I still haven’t figured out how to replicate these in lower DOCTYPEs – which is why I asked you to remove the Actions from your page before validating the basic layout. The invalidities it adds to the page are NOT the type that would affect things in JavaScript, though. The things that really matter there are duplicate IDs or improperly-nested content.
Walter
On Feb 28, 2013, at 10:56 AM, Simon K wrote:
Hi Walter,
Are you saying that you need to see the original page to diagnose the fault?
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Okay, this is updated (0.1.11) and tested and working in Firefox. Move borders to the outside works again now.
Walter
On Feb 28, 2013, at 2:43 PM, Walter Lee Davis wrote:
You have indeed found a bug. Sorry to have doubted you. Moving borders to the outside appears to fail in Firefox.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
So, if I’m already using Carousel 2, all I do is simply replace my existing Carousel 2 Action and then republish the site? Is dragging it and dropping it in the FWP actions folder sufficient or should it be installed?
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Yes, you update the Action and re-publish, and it should just work. To update an Action, you can drag it into the Actions folder, and make sure when you do that you get an alert from Finder saying that you are replacing an existing file. If you don’t see that alert, you will have to figure out why that is – you may have downloaded both Actions to your Downloads folder, and Finder may have added a .1 to one of them to disambiguate them, since you cannot have two files in the same folder with the same name.
Walter
On Mar 2, 2013, at 11:03 PM, RavenManiac wrote:
So, if I’m already using Carousel 2, all I do is simply replace my existing Carousel 2 Action and then republish the site? Is dragging it and dropping it in the FWP actions folder sufficient or should it be installed?
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
My recommended method for updating Actions is one that NEVER FAILS (and which unfortunately I am often forced to follow since Freeway does not reliably allow me to “double-click to install”):
Walter, I just tested your 0.1.11. No changes that I see in my implementation of Carousel2, which is fine. The updated doesn’t fix the IE7 problem whereby the content gets duplicated and splatters over the screen, but I didn’t expect that. Just wanted to give you feedback on the latest version.
–James Wages
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options