My problem has been going on for 1 year and I am just ready to deal with it now.
The effect I went for when I created my site with fw was to have everything hidden on the page at first (used transtion fx action with delay)…and then have 20 icons fade in 1 after each other, then the rest of the site appear.
I noticed this last year that mostly with ipads and ie on PC and generally many other times, there was a FLASH of showing those things that should have been hidden, and then it proceeds to load in the page. It looked sloppy and unpro.
So now I have taken off the delay for everything (the items now appear right away when you get to the site) but the 20 icons which fade in on timer all come in as a delay as they should. This has resulted in the icons FLASHING when you first arrive (bad).
I figure the reason is because the site is seeing the graphics before the timer or something like that.
Is there a way to have items come in after a little delay, WITHOUT a flash of them first? Maybe this has to do with the layering?
Thanks
here is the site…
Barry
p.s. Dave you will be happy I have gotten rid of the Welcome screen finally to help with all this.
There’s two different ways to solve this, one of which will cause a serious usability problem for anyone who doesn’t have JavaScript enabled.
First, the underlying problem is overall file size (HTML + images) – cut that down to the barest minimum, and your problem will solve itself. Freeway uses the best-practice technique of using JavaScript to hide things that will be revealed later with more JavaScript. The win here is that nobody who can’t see the reveal will be stuck with a page where that initially-hidden content is permanently hidden. This requires a fast browser – and a lean page – in order to work smoothly.
So the other solution possible (if you can’t make the page any smaller) is to use the Extended dialog to set the following style on the elements you want to reveal with TFX:
display: none
You select each fade-in element, open up the Item/Extended dialog, click on the DIV Style tab, and then New. In Name, you put display and in Value, you put none. Okay out of the stack, and repeat.
This is the same thing that the Action does, only you’re doing it in CSS, which will be evaluated before the JavaScript is run, so there’s hardly any chance of a “flash of unstyled content” happening here. As I mentioned, the down-side to this is that anyone who hasn’t enabled JavaScript in their browser will never see these elements at all. Anyone who is using a screen reader (visually disabled) will probably not be told that these elements exist, either (not entirely sure about that last part, it’s just a suspicion).
Walter
On Apr 12, 2013, at 12:25 PM, Barry Hoffman wrote:
Is there a way to have items come in after a little delay, WITHOUT a flash of them first? Maybe this has to do with the layering?
Hi Walter,
The solution here is to create a class style for the hidden items (called .hidden maybe), apply this to all of the items that need to be hidden on page load, but additionally add a noscript block that overwrites the hidden style and makes them all appear again if the user has JavaScript switched off.
So for example in my document outline we’d have;
<html>
<head>
<style>
.hidden { display:none }
</style>
<noscript>
<style>
.hidden { display:block }
</style>
</noscript>
</head>
<body>
<div class="hidden"></div>
<div class="hidden"></div>
<div class="hidden"></div>
<script>
/* Some JavaScript down here that displays the hidden items after a short delay */
</script>
</body>
</html>
If the user has JavaScript enabled the CSS will hide the items and the JavaScript will then show them again after a short delay. If, however, JavaScript is disabled the .hidden style is loaded and then almost instantly reset even before the items on the page are loaded which should prevent them from flickering on the page.
Regards,
Tim.
On 12 Apr 2013, at 18:15, Walter Lee Davis wrote:
This is the same thing that the Action does, only you’re doing it in CSS, which will be evaluated before the JavaScript is run, so there’s hardly any chance of a “flash of unstyled content” happening here. As I mentioned, the down-side to this is that anyone who hasn’t enabled JavaScript in their browser will never see these elements at all. Anyone who is using a screen reader (visually disabled) will probably not be told that these elements exist, either (not entirely sure about that last part, it’s just a suspicion).
They wear tin-foil hats and are worried about the gubmint spying on them. They work for a company that has an IT department with too little to do all day. They are using an early “smart” phone with the same processing power as a solar calculator. There’s lots of possible reasons. It’s not rare enough to never worry about it.
Walter
On Apr 12, 2013, at 1:32 PM, Barry Hoffman wrote:
Walt
Can you give me an idea when or why someone would not have js enabled in browser? Students? Family computers… School?
Hi all,
i was using that effect on several websites and it worked perfect for a time. Then, maybe after one year the “flashing” Barry described above, occurs in Safari and Chrome, Firefox is still ok. Thats very annoying.
I think Softpress should have a look at this issue because in this case, transistion fx isn’t fully useable. It is not very handy to follow the steps of Walter and Tim every time s.o. wants to use that effect. To be handy we need actions of Softpress, that work correctly and without a half-life period.
Guys, as things are going along well, I am just having 1 small hiccup regarding hiding the first frame of my carousel.
It seems that when I put just the Tansition FX delay on the main HTML container of the CAROUSEL which has the graphic in it, the action works fine (but flashes).
But when I add all those Extend, hidden and class things from Walt and Tim to the carousel, the carousel NEVER APPEARS. I was expecting the carousel to come in at 4 seconds just like all the other graphics that I did it to.
When you look, you will see how there is a big space where the carousel never comes in. Is there a conflict of some sort?
Thanks,
Barry
(There still may be flashing of the 23 icons since I have not done them yet with the Walt/Tim stuff)
If you search on this list, I remember there was a conflict betw. Tansition FX and CAROUSEL some time ago.
/me having problems with Carousel myself!
/ Omar
::: Communication to improve civilisation :::
s_ip
On 13 apr 2013, at 12:44, “Barry Hoffman” email@hidden wrote:
Yes Tim,
Guys, as things are going along well, I am just having 1 small hiccup regarding hiding the first frame of my carousel.
It seems that when I put just the Tansition FX delay on the main HTML container of the CAROUSEL which has the graphic in it, the action works fine (but flashes).
But when I add all those Extend, hidden and class things from Walt and Tim to the carousel, the carousel NEVER APPEARS. I was expecting the carousel to come in at 4 seconds just like all the other graphics that I did it to.
When you look, you will see how there is a big space where the carousel never comes in. Is there a conflict of some sort?
Carousel (the original) massively re-arranges the page, and only writes the code it expects to be present into the resulting page. The only way I can see this working the way you want it to is if you draw an HTML box large enough to contain the Carousel, apply your presto-fade-appear effect to that box, and then build your Carousel as a nested positioned child of that first box. There are two ways to move an HTML box into another box as a nested positioned child: you can use the Site pane, toggled over to Page view, and by dragging one box name up and to the right underneath another, you can cause a parent/child relationship to be made. The other way to do it is to start dragging the child element until the pointer is over the parent box, then press the spacebar (without lifting the mouse button) to indicate that you want the parent to become the parent of the item you are dragging. The border of the parent box will glow blue to indicate this relationship.
Walter
On Apr 13, 2013, at 6:44 AM, Barry Hoffman wrote:
Yes Tim,
Guys, as things are going along well, I am just having 1 small hiccup regarding hiding the first frame of my carousel.
It seems that when I put just the Tansition FX delay on the main HTML container of the CAROUSEL which has the graphic in it, the action works fine (but flashes).
But when I add all those Extend, hidden and class things from Walt and Tim to the carousel, the carousel NEVER APPEARS. I was expecting the carousel to come in at 4 seconds just like all the other graphics that I did it to.
When you look, you will see how there is a big space where the carousel never comes in. Is there a conflict of some sort?
I have never written any of my effect-heavy Actions to be aware of FX transforms, as I consider that to be too much icing and not enough cake. I can’t say for certain if there would be any issue with Carousel 2 or not, you can certainly try it and see.
Walter
On Apr 13, 2013, at 9:51 AM, Barry Hoffman wrote:
ok Walt will try these. is there a “newer” carousel type I should use to make this happen or just go ahead with what you suggested?
Walt, I just saw the Carousel2. looks improved, saw a comment about maybe not having what the other had…
does it have the ability to be paused and then started like the original?
I did it. I do not know how , but I think it works…
It uses the original carousel (not sure if it matters), I put the carousel over a graphic (not sure of it matters) and applied the transition fx delay to carousel and now it seems to come in on delay with NO FLASH.
