I’m announcing a new release of my Sliding Notes plugin. It resolves a CSS conflict with Shadowbox JS , another popular WordPress plugin (hence the release name). At the same time, with this release I’m relieving the user from housekeeping the CSS parts that are vital to Sliding Notes function, but unrelated to its visual appearance.
With Sliding Notes versions prior to 1.4 you had to manually add .hidden and .block CSS clauses to your stylesheet. Please remove them again. As of Sliding Notes 1.4, these clauses are automatically added where needed.
ATTENTION Users of Shadowbox JS
If you have applied the conflict workaround, and commented out the .hidden clause in your extras.css file, you need to uncomment it again! (Look for it in the wp-content/plugins/shadowbox-js/css/ folder.)
In the past, there have been some reports of a curious Sliding Notes effect, where Notes were initially open on some sites. I could immediately trace the cause down to a CSS conflict with the ‘Shadowbox JS’ plugin, and advice a quick workaround, one that could be easily, alas manually, applied.
The Conflict, And The Workaround
To Sliding Notes’ function, two CSS clauses are utterly vital: .hidden and .block. Not only there presence and their contents are essential, but also their ordering. Failing to preserve CSS ordering results in some pretty weird effects, from unaesthetic, cross-browser related dynamic effects when the notes are being shown, to the notes not being initially collapsed.
Shadowbox JS’ includes some stylesheets of own, extras.css being one of them. It contains a .hidden CSS clause. This clause effectively “spoils” the aforesaid utterly sensitive CSS clause ordering, causing the unwanted effect.
Once the cause was found, a workaround became immediately obvious: Commenting out the .hidden clause in extras.css ultimately resolved the conflict.
The Problem With The Workaround
Of course, I wasn’t too happy about a state of affairs where users had to adjust their other stuff in order to use Sliding Notes.
I was even less happy with putting a burden on users to manually ensure CSS vital to the plugins function is included correctly. I figured, CSS related to visual appearance belongs in the hands of the user, but CSS related to function should be sole responsibility of the plugin.
With these thoughts on my mind, I made a few tests if separating the functional CSS from the rest and injecting it programatically by the plugin would resolve the Shadowbox JS conflict as well.
So here it is, the brand new Shadowchaser release of Sliding Notes. It has successfully chased the “shadows of it’s past”.
Cheers and happy sliding.
- Sliding Notes Plugin Is Here
- Sliding Notes Major Upgrade
- Slinding Notes - 1.1 Series Withdrawal
- Sliding Notes Back On Air
- Sliding Notes 1.2.1 Released
- Sliding Notes 1.3 - Hot New "Presidential Oath" Release
- Sliding Notes 1.4 - Shadowchaser Release
- Sliding Notes 1.4.1 Released
- Sliding Notes 1.5.0 "Accordion Virtuoso"
- Sliding Notes 1.6 - "W3C Tribute"