Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
A problem with blocks that are collapsed by default, is that on page load, there is an unwanted fraction of a second that shows the blocks in expanded state, after which they are collapsed.
Is it possible to prevent the page from displaying the block, and render the collapsed block after Drupal has understood that the block is collapsed?
The same annoying effect i see with logintoboggan by the way. I can't imagine that there is not a solution to prevent this.
Comment | File | Size | Author |
---|---|---|---|
#4 | collapsiblock-preset-state-1291712-4.patch | 722 bytes | darvanen |
Comments
Comment #1
Anonymous (not verified) CreditAttribution: Anonymous commentedThe blocks CSS is open, and it requires JavaScript (which is run after page load) to collapse them. So it is inevitable to see them open for a fraction.
Comment #2
polskikrol CreditAttribution: polskikrol commentedSubscribe.
Wonder if there are any hooks to make it workaround the fact that the content loads with the block CSS open.
Comment #3
darvanenPossible improvement for V2.
Comment #4
darvanenThis can be done when the theme in use implements content_attributes in the block template, otherwise the JS will kick in as fallback.
Comment #5
darvanen