Frank Cook wrote:
(a) Eric is right, of course. I'm curious as to why the custom attribute was used on each of the containers with the class of 'step-container'. At first sight, item (b) below seems to achieve the same as the custom attribute, but automatically.

(b) It seems that the next step was to go to the 'In State' section, choose 'Out of View', and in Design > Filters & Blend Modes set the opacity to zero.

(c) In the Regular state, Effects section, a New Transition was set with a Duration 1 second and Delay 1 second.

Can someone perhaps explain the matter that provoked my curiosity at (a) above please?

Thanks.
Frank

Eric Rohloff wrote:
They are adding the data-outofview="true" to the elements.
Use Custom and put data-outofview for name and true in for value
Then set a transition looks like they have it set to Ease Duration 1 Delay .5

Wayan Jaya wrote:
In microsoft edge, I get the "Out Of Viw transitions reversed (in other words out of view = opacity =0 regular = opacity 1)
but in egge it gets reversed I am sure that with SD v2.5 (maybe even early SDv3) this didn't occur
anyone else experiencing this???

Frank Cook wrote:

Yes, Edge does seem to cause a different effect for me also: instead of the containers starting with zero opacity, they scroll into view fully visible, then go to opacity zero, and then return to full visibility.

I have no knowledge of the technicalities involved, and the following are simply speculations based on my observations of what seems to happen.
1. On first going to a web page containing elements with an out-of-view state,
(a) most browsers seem to treat those elements as having been out of view until the page has loaded;
(b) the Edge browser seems to treat those elements as initially in-view and then out-of-view and then back in-view.
2. On first going to a web page,
(a) most browsers seem to load the whole page straight away, so that scrolling is a matter of bringing into view what has already been loaded;
(b)the Edge browser seems to load straight away just the part of the page that is needed to be shown immediately in the browser window, and loads items scrolled to as the scrolling occurs.

The combination of the two items in the preceding paragraph would perhaps explain the effect mentioned in the first paragraph above.

Frank
Hi Frank
That sounds like a good theory
EXCEPT in RSD 2.5 Microsoft Edge behaves exactly how it should do with out of view ~ opacity ~ or any other transition one uses. It's only with SD V3.5 that it is posterior about,, so my conclusion is that it has to be something wrong with the tecky stuff in SDv3.5