Be notified of new releases
Create your free GitHub account today to subscribe to this repository for new releases and build software alongside 28 million developers.Sign up
- Absent mindedly forgot to bump npm version #183
imageloaddonecustom event, even though it's in the readme (and previously implemented): #184
- Borked image link on demo page (the first image): #185
- Incorrect parsing of HTML5
- Failure to update the
instanceDataobject during manually fired close event on Fluidbox now fixed. Custom close triggers will now update the instance data on Fluidbox elements correctly.
- Turned off z-index optimisation by CSSnano
- Fixed IE8 error when the
consoleobject is not recognized (thanks @maxee)
- Close event will do nothing if instance data is unavailable, or set to 0. Micro-optimisation perhaps, but still good to have.
Informative URL handling messages:
Fluidbox will throw a warning and refuse to proceed if whitespace characters are present in the URL. As HTML collapses multiple whitespaces into one, it is impossible to determine whether the reference file contains collapsed or uncollapsed multiple whitespaces. Whitespaces must be escaped manually.
On the other hand, Fludibox throws a warning but proceeds with expected behaviour when encountering the following character set (expressed in regex):
["'\(\)]. The reason being that these characters directly interfere with jQuery and therefore need to be replaced anyway.
Minor bug fix:
A minor bug was found when Fluidbox fails to unbind event listeners, due to a syntax error (separation of event listeners using
, instead of just a whitespace
.off()method). This issue is fixed now so that the
.destroy() method works as intended.
After rewriting the entire codebase over the course of summer, Fluidbox v2.0 is ready to debut!
This release consists of mostly restructuring the codebase of Fluidbox into a more verbose yet friendly form, based on the extended version of jQuery Boilerplate. Most of the issues filed have also been resolved.
Many considerations were taken into place when rewriting the codebase, and therefore Fluidbox 2.0 has dropped several configuration options and custom emitted events to further simplify the plugin. Remember to check the updated readme and demo pages for further documentation and usage examples.
Fluidbox v2.0 supports calling several public methods through the .fluidbox() method, allowing users to programatically open, close, reposition, recalculate, bind/unbind events associated with Fluidbox instances.
Finally, Grunt has been integrated into the project to make building the files a lot speedier and convenient. Grunt dependencies are listed in the readme, and the scripts are available in the repo.
- Enabled the option to trigger immediate opening of Fluidbox. This has to be turned on manually, by setting `immediateOpen` to `true` during initialization.
- Added five new custom events that are triggered.
- Rearranged some code with regards to opening and closing of Fluidbox instances for better readability, fixed indentation inconsistencies in original JS file.
- Added an animated CSS loader to Fluidbox instances, exceptionally important for delayed opening setups (default setup) as users are often unaware if Fluidbox has failed, or simply waiting for target image to be preloaded. The appearance of the loader is purely controlled by a CSS pseudo-element, activated upon the addition of `.fluidbox-loading` class.
- The stylesheet of Fluidbox has been ported over to LESS, in addition to SCSS.
Fluidbox now allows users to trigger manual recomputing of the dimensions of the overlay and that of the active Fluidbox instance. This functionality is extremely useful when you make layout changes that repaints the canvas and alters the dimensions of linked Fluidbox images. In order to do so, you will have to trigger the event manually, after the changes in the DOM, or element dimensions has been applied.
Once this manual trigger is made, it will trigger a custom event called
recomputeend. This is distinct from the
resizeend event in the sense that it is not triggered by the
On a side note, this version also comes with a crucial fix that causes the
closeTrigger settings to propagate to all instances of Fluidboxes on the same page, even though it was only specified for a subset of instances. This bug has been present since the first release and it was only discovered and fixed as of now.
Custom events have arrived at Fluidbox—now you are able to listen to five distinct events triggered during different stages of an active Fluidbox instance, and add your own application-specific callbacks when necessary. The documentation has been updated to reflect this, and so is the demo. The five custom events supported are: