Hi,
I'm not sure if this is a bug or if there's something that I'm missing?
I checked off "Start Slideshow Paused" under the Views Slideshow's "Single Frame Options" settings but can't seem to get to work.
I configured it to display the controls "Previous", "Pause"/"Resume", "Next".
When I clear the browser's history/cache & then visit the site, the slideshow view, which is in a block, does start out paused (& the link displayed is "Resume"); however, when I click on a different page, the "Resume" is changed to the "Pause" link and the slideshow is no longer paused.
Thus, it does not appear that "Start Slideshow Paused" works properly. The setting is correct on the first page visited but it does not remain the same throughout the whole browser session, even though the "Resume" link was never clicked.
Has anybody had this issue or have any suggestions on resolving it? Thanks.
Comments
Comment #1
redndahead commentedProbably would be fixed by #841566: Make sure all strings that should be numbers are set to numbers and all strings that should be booleans are set to booleans
Comment #2
redndahead commentedPlease check the next dev release and tell me if it is fixed for you.
Comment #3
new_B commentedHi redndahead,
I checked the dev version & it didn't fix the issue; however, I checked again and did some further tests. I realized that it is another issue altogether. Sorry for missing the actual issue, which is the following:
(1) "Pause When the Slideshow is Not Visible" was checked off in addition to
(2) "Start Slideshow Paused".
When (1) is not selected, "Start Slideshow Paused" works as expected;
However, when it is selected, the "Start Slideshow Paused" option does not work properly. When the block with the slideshow is in full display, the "Resume" button appears as expected.
However, when the block is not in full display on the screen, and you scroll down, the "Pause" link appears, which may be #(1) taking precedence over #(2). Not sure if this is a bug or by design?
Thanks.
Comment #4
redndahead commentednever moved back to active. Putting back
Comment #5
redndahead commentedSo this is a hard one. Which one takes precedence? Should we only resume on hidden only if something else didn't pause it? Should we keep track of what paused it? We have the same problem with hovering over with a mouse. I have done some solving of this in 3.x, but not sure how to apply it for the 2.x line.
Comment #6
redndahead commentedComment #7
redndahead commentedI'm marking this as won't fix. A solution has been presented in 3.x and I feel comfortable saying upgrade to that and it will be fixed.