fullPage plugin by Alvaro Trigo. Create full screen pages fast and simple

Overview

fullPage.js

preview compatibility

English | Español | Français | Pусский | 中文 | 한국어

Available for Vue, React and Angular.


fullPage.js version License PayPal Donate jsDelivr Hits    |   7Kb gziped   |   Created by @imac2


A simple and easy to use library that creates fullscreen scrolling websites (also known as single page websites or onepage sites) and adds landscape sliders inside the sections of the site.

Introduction

Suggestion are more than welcome, not only for feature requests but also for coding style improvements. Let's make this a great library to make people's lives easier!

Compatibility

fullPage.js is fully functional on all modern browsers, as well as some old ones such as Internet Explorer 9, Opera 12, etc. It works with browsers with CSS3 support and with the ones which don't have it, making it ideal for old browsers compatibility. It also provides touch support for mobile phones, tablets and touch screen computers.

Special thanks to Browserstack for supporting fullpage.js.

License

Commercial license

If you want to use fullPage to develop non open sourced sites, themes, projects, and applications, the Commercial license is the appropriate license. With this option, your source code is kept proprietary. Which means, you won't have to change your whole application source code to an open source license. [Purchase a Fullpage Commercial License]

Open source license

If you are creating an open source application under a license compatible with the GNU GPL license v3, you may use fullPage under the terms of the GPLv3.

The credit comments in the JavaScript and CSS files should be kept intact (even after combination or minification)

Read more about fullPage's license.

Usage

As you can see in the example files, you will need to include:

  • The JavaScript file fullpage.js (or its minified version fullpage.min.js)
  • The css file fullpage.css

Optionally, when using css3:false, you can add the easings file in case you want to use other easing effects apart from the one included in the library (easeInOutCubic).

Install using bower or npm

Optionally, you can install fullPage.js with bower or npm if you prefer:

Terminal:

// With bower
bower install fullpage.js

// With npm
npm install fullpage.js

Including files:

<link rel="stylesheet" type="text/css" href="fullpage.css" />

<!-- This following line is optional. Only necessary if you use the option css3:false and you want to use other easing effects rather than "easeInOutCubic". -->
<script src="vendors/easings.min.js"></script>


<!-- This following line is only necessary in the case of using the option `scrollOverflow:true` -->
<script type="text/javascript" src="vendors/scrolloverflow.min.js"></script>

<script type="text/javascript" src="fullpage.js"></script>

Using Webpack, Browserify or Require.js? Check how to use fullPage.js with module loaders.

Optional use of CDN

If you prefer to use a CDN to load the needed files, fullPage.js is in CDNJS: https://cdnjs.com/libraries/fullPage.js

Required HTML structure

Start your HTML document with the compulsory HTML DOCTYPE declaration on the 1st line of your HTML code. You might have troubles with sections heights otherwise. The examples provided use HTML 5 doctype <!DOCTYPE html>.

Each section will be defined with an element containing the section class. The active section by default will be the first section, which is taken as the home page.

Sections should be placed inside a wrapper (<div id="fullpage"> in this case). The wrapper can not be the body element.

<div id="fullpage">
	<div class="section">Some section</div>
	<div class="section">Some section</div>
	<div class="section">Some section</div>
	<div class="section">Some section</div>
</div>

If you want to define a different starting point rather than the first section or the first slide of a section, just add the class active to the section and slide you want to load first.

<div class="section active">Some section</div>

In order to create a landscape slider within a section, each slide will be defined by default with an element containing the slide class:

<div class="section">
	<div class="slide"> Slide 1 </div>
	<div class="slide"> Slide 2 </div>
	<div class="slide"> Slide 3 </div>
	<div class="slide"> Slide 4 </div>
</div>

You can see a fully working example of the HTML structure in the simple.html file.

Initialization

Initialization with Vanilla Javascript

All you need to do is call fullPage.js before the closing </body> tag.

new fullpage('#fullpage', {
	//options here
	autoScrolling:true,
	scrollHorizontally: true
});

//methods
fullpage_api.setAllowScrolling(false);

Initialization with jQuery

You can use fullpage.js as a jQuery plugin if you want to!

$(document).ready(function() {
	$('#fullpage').fullpage({
		//options here
		autoScrolling:true,
		scrollHorizontally: true
	});

	//methods
	$.fn.fullpage.setAllowScrolling(false);
});

Functions and methods can still be called in the jQuery way, as in fullPage.js v2.X.

Vanilla JS example with all options

A more complex initialization with all options set could look like this:

var myFullpage = new fullpage('#fullpage', {
	//Navigation
	menu: '#menu',
	lockAnchors: false,
	anchors:['firstPage', 'secondPage'],
	navigation: false,
	navigationPosition: 'right',
	navigationTooltips: ['firstSlide', 'secondSlide'],
	showActiveTooltip: false,
	slidesNavigation: false,
	slidesNavPosition: 'bottom',

	//Scrolling
	css3: true,
	scrollingSpeed: 700,
	autoScrolling: true,
	fitToSection: true,
	fitToSectionDelay: 1000,
	scrollBar: false,
	easing: 'easeInOutCubic',
	easingcss3: 'ease',
	loopBottom: false,
	loopTop: false,
	loopHorizontal: true,
	continuousVertical: false,
	continuousHorizontal: false,
	scrollHorizontally: false,
	interlockedSlides: false,
	dragAndMove: false,
	offsetSections: false,
	resetSliders: false,
	fadingEffect: false,
	normalScrollElements: '#element1, .element2',
	scrollOverflow: false,
	scrollOverflowReset: false,
	scrollOverflowOptions: null,
	touchSensitivity: 15,
	bigSectionsDestination: null,

	//Accessibility
	keyboardScrolling: true,
	animateAnchor: true,
	recordHistory: true,

	//Design
	controlArrows: true,
	verticalCentered: true,
	sectionsColor : ['#ccc', '#fff'],
	paddingTop: '3em',
	paddingBottom: '10px',
	fixedElements: '#header, .footer',
	responsiveWidth: 0,
	responsiveHeight: 0,
	responsiveSlides: false,
	parallax: false,
	parallaxOptions: {type: 'reveal', percentage: 62, property: 'translate'},
	dropEffect: false,
	dropEffectOptions: { speed: 2300, color: '#F82F4D', zIndex: 9999},
	cards: false,
	cardsOptions: {perspective: 100, fadeContent: true, fadeBackground: true},

	//Custom selectors
	sectionSelector: '.section',
	slideSelector: '.slide',

	lazyLoading: true,

	//events
	onLeave: function(origin, destination, direction){},
	afterLoad: function(origin, destination, direction){},
	afterRender: function(){},
	afterResize: function(width, height){},
	afterReBuild: function(){},
	afterResponsive: function(isResponsive){},
	afterSlideLoad: function(section, origin, destination, direction){},
	onSlideLeave: function(section, origin, destination, direction){}
});

Creating links to sections or slides

If you are using fullPage.js with anchor links for the sections (using the anchors option or the attribute data-anchor in each section), then you will be able to use anchor links also to navigate directly to a certain slide inside a section.

This would be an example of a link with an anchor: http://alvarotrigo.com/fullPage/#secondPage/2 (which is the URL you will see once you access to that section/slide manually) Notice the last part of the URL ends in #secondPage/2.

Having the following initialization:

new fullpage('#fullpage', {
	anchors:['firstPage', 'secondPage', 'thirdPage']
});

The anchor at the end of the URL #secondPage/2 defines the section and slide of destination respectively. In the previous URL, the section of destination will be the one defined with the anchor secondPage and the slide will be the 2nd slide, as we are using the index 2 for it. (the fist slide of a section has index 0, as technically it is a section).

We could have used a custom anchor for the slide instead of its index if we would have used the attribute data-anchor on the HTML markup like so:

<div class="section">
	<div class="slide" data-anchor="slide1"> Slide 1 </div>
	<div class="slide" data-anchor="slide2"> Slide 2 </div>
	<div class="slide" data-anchor="slide3"> Slide 3 </div>
	<div class="slide" data-anchor="slide4"> Slide 4 </div>
</div>

In this last case, the URL we would use would be #secondPage/slide3, which is the equivalent to our previous #secondPage/2.

Note that section anchors can also be defined in the same way, by using the data-anchor attribute, if no anchors array is provided.

Be careful! data-anchor tags can not have the same value as any ID element on the site (or NAME element for IE).

Creating smaller or bigger sections

Demo fullPage.js provides a way to remove the full height restriction from its sections and slides. It is possible to create sections which height is smaller or bigger than the viewport. This is ideal for footers. It is important to realise that it doesn't make sense to have all of your sections using this feature. If there is more than one section in the initial load of the site, fullPage.js won't scroll at all to see the next one as it will be already in the viewport.

To create smaller sections just use the class fp-auto-height in the section you want to apply it. It will then take the height defined by your section/slide content.

<div class="section">Whole viewport</div>
<div class="section fp-auto-height">Auto height</div>

Responsive auto height sections

Demo A responsive auto height can be applied by using the class fp-auto-height-responsive. This way sections will be fullscreen until the responsive mode gets fired. Then they'll take the size required by their content, which could be bigger or smaller than the viewport.

State classes added by fullpage.js

Fullpage.js adds multiple classes in different elements to keep a record of the status of the site:

  • active is added the current visible section and slide.
  • active is added to the current menu element (if using the menu option).
  • A class of the form fp-viewing-SECTION-SLIDE is added to the body element of the site. (eg: fp-viewing-secondPage-0) The SECTION and SLIDE parts will be the anchors (or indexes if no anchor is provided) of the current section and slide.
  • fp-responsive is added to the body element when the entering in the responsive mode
  • fp-enabled is added to the html element when fullpage.js is enabled. (and removed when destroyed).
  • fp-destroyed is added to the fullpage.js container when fullPage.js is destroyed.

Lazy Loading

Demo fullPage.js provides a way to lazy load images, videos and audio elements so they won't slow down the loading of your site or unnecessarily waste data transfer. When using lazy loading, all these elements will only get loaded when entering in the viewport. To enable lazy loading all you need to do is change your src attribute to data-src as shown below:

<img data-src="image.png">
<video>
	<source data-src="video.webm" type="video/webm" />
	<source data-src="video.mp4" type="video/mp4" />
</video>

If you already use another lazy load solution which uses data-src as well, you can disable the fullPage.js lazy loading by setting the option lazyLoading: false.

Auto play/pause embedded media

Demo Note: the autoplay feature might not work on some mobile devices depending on the OS and browser (i.e. Safari on iOS version < 10.0).

Play on section/slide load:

Using the attribute autoplay for videos or audio, or the param autoplay=1 for youtube iframes will result in the media element playing on page load. In order to play it on section/slide load use instead the attribute data-autoplay. For example:

<audio data-autoplay>
	<source src="http://metakoncept.hr/horse.ogg" type="audio/ogg">
</audio>

Pause on leave

Embedded HTML5 <video> / <audio> and Youtube iframes are automatically paused when you navigate away from a section or slide. This can be disabled by using the attribute data-keepplaying. For example:

<audio data-keepplaying>
	<source src="http://metakoncept.hr/horse.ogg" type="audio/ogg">
</audio>

Use extensions

fullpage.js provides a set of extensions you can use to enhance its default features. All of them are listed as fullpage.js options.

Extensions requires you to use the minified file fullpage.extensions.min.js that is inside the dist folder instead of the usual fullPage.js file (fullpage.js or fullpage.min.js).

Once you acquire the extension file, you will need to add it before fullPage. For example, if I want to use the Continuous Horizontal extension, I would have include the extension file and then the extensions version of the fullPage file.

<script type="text/javascript" src="fullpage.continuousHorizontal.min.js"></script>
<script type="text/javascript" src="fullpage/fullpage.extensions.min.js"></script>

An activation key and a license key will be required for each extension. See more details about it here.

Then you will be able to use and configure them as explained in options.

Options

  • licenseKey: (default null). This option is compulsory. If you use fullPage in a non open source project, then you should use the license key provided on the purchase of the fullPage Commercial License. If your project is open source and it is compatible with the GPLv3 license you can request a license key. Please read more about licenses here and on the website. For example:
new fullpage({
    licenseKey: 'YOUR_KEY_HERE'
});
  • v2compatible: (default false). Determines whether to make it 100% compatible with any code written for version 2, ignoring new features or api changes of version 3. State classes, callbacks signature etc. will work exactly in the same way as it did on verion 2. Note that this option will be removed at some point in the future..

  • controlArrows: (default true) Determines whether to use control arrows for the slides to move right or left.

  • verticalCentered: (default true) Vertically centering of the content within sections. When set to true, your content will be wrapped by the library. Consider using delegation or load your other scripts in the afterRender callback.

  • scrollingSpeed: (default 700) Speed in milliseconds for the scrolling transitions.

  • sectionsColor: (default none) Define the CSS background-color property for each section. Example:

new fullpage('#fullpage', {
	sectionsColor: ['#f2f2f2', '#4BBFC3', '#7BAABE', 'whitesmoke', '#000'],
});
  • anchors: (default []) Defines the anchor links (#example) to be shown on the URL for each section. Anchors value should be unique. The position of the anchors in the array will define to which sections the anchor is applied. (second position for second section and so on). Using anchors forward and backward navigation will also be possible through the browser. This option also allows users to bookmark a specific section or slide. Be careful! anchors can not have the same value as any ID element on the site (or NAME element for IE). Now anchors can be defined directly in the HTML structure by using the attribute data-anchor as explained here.

  • lockAnchors: (default false) Determines whether anchors in the URL will have any effect at all in the library. You can still using anchors internally for your own functions and callbacks, but they won't have any effect in the scrolling of the site. Useful if you want to combine fullPage.js with other plugins using anchor in the URL.

Important It is helpful to understand that the values in the anchors option array correlate directly to the element with the class of .section by it's position in the markup.

  • easing: (default easeInOutCubic) Defines the transition effect to use for the vertical and horizontal scrolling. It requires the file vendors/easings.min.js or jQuery UI for using some of its transitions. Other libraries could be used instead.

  • easingcss3: (default ease) Defines the transition effect to use in case of using css3:true. You can use the pre-defined ones (such as linear, ease-out...) or create your own ones using the cubic-bezier function. You might want to use Matthew Lein CSS Easing Animation Tool for it.

  • loopTop: (default false) Defines whether scrolling up in the first section should scroll to the last one or not.

  • loopBottom: (default false) Defines whether scrolling down in the last section should scroll to the first one or not.

  • loopHorizontal: (default true) Defines whether horizontal sliders will loop after reaching the last or previous slide or not.

  • css3: (default true). Defines whether to use JavaScript or CSS3 transforms to scroll within sections and slides. Useful to speed up the movement in tablet and mobile devices with browsers supporting CSS3. If this option is set to true and the browser doesn't support CSS3, a fallback will be used instead.

  • autoScrolling: (default true) Defines whether to use the "automatic" scrolling or the "normal" one. It also has affects the way the sections fit in the browser/device window in tablets and mobile phones.

  • fitToSection: (default true) Determines whether or not to fit sections to the viewport or not. When set to true the current active section will always fill the whole viewport. Otherwise the user will be free to stop in the middle of a section.

  • fitToSectionDelay: (default 1000). If fitToSection is set to true, this delays the fitting by the configured milliseconds.

  • scrollBar: (default false) Determines whether to use scroll bar for the vertical sections on site or not. In case of using scroll bar, the autoScrolling functionality will still work as expected. The user will also be free to scroll the site with the scroll bar and fullPage.js will fit the section in the screen when scrolling finishes.

  • paddingTop: (default 0) Defines the top padding for each section with a numerical value and its measure (paddingTop: '10px', paddingTop: '10em'...) Useful in case of using a fixed header.

  • paddingBottom: (default 0) Defines the bottom padding for each section with a numerical value and its measure (paddingBottom: '10px', paddingBottom: '10em'...). Useful in case of using a fixed footer.

  • fixedElements: (default null) Defines which elements will be taken off the scrolling structure of the plugin which is necessary when using the css3 option to keep them fixed. It requires a string with the Javascript selectors for those elements. (For example: fixedElements: '#element1, .element2')

  • normalScrollElements: (default null) Demo If you want to avoid the auto scroll when scrolling over some elements, this is the option you need to use. (useful for maps, scrolling divs etc.) It requires a string with the Javascript selectors for those elements. (For example: normalScrollElements: '#element1, .element2'). This option should not be applied to any section/slide element itself.

  • bigSectionsDestination: (default null) Demo Defines how to scroll to a section which height is bigger than the viewport and when not using scrollOverflow:true. (Read how to create smaller or bigger sections). By default fullPage.js scrolls to the top if you come from a section above the destination one and to the bottom if you come from a section below the destination one. Possible values are top, bottom, null.

  • keyboardScrolling: (default true) Defines if the content can be navigated using the keyboard.

  • touchSensitivity: (default 5) Defines a percentage of the browsers window width/height, and how far a swipe must measure for navigating to the next section / slide

  • continuousVertical: (default false) Defines whether scrolling down in the last section should scroll down to the first one and if scrolling up in the first section should scroll up to the last one. Not compatible with loopTop, loopBottom or any scroll bar present in the site (scrollBar:true or autoScrolling:false).

  • continuousHorizontal: (default false) Extension of fullpage.js. Defines whether sliding right in the last slide should slide right to the first one or not, and if scrolling left in the first slide should slide left to the last one or not. Not compatible with loopHorizontal. Requires fullpage.js >= 3.0.1.

  • scrollHorizontally: (default false) Extension of fullpage.js. Defines whether to slide horizontally within sliders by using the mouse wheel or trackpad. It can only be used when using: autoScrolling:true. Ideal for story telling. Requires fullpage.js >= 3.0.1.

  • interlockedSlides: (default false) Extension of fullpage.js. Determines whether moving one horizontal slider will force the sliding of sliders in other section in the same direction. Possible values are true, false or an array with the interlocked sections. For example [1,3,5] starting by 1. Requires fullpage.js >= 3.0.1.

  • dragAndMove: (default false) Extension of fullpage.js. Enables or disables the dragging and flicking of sections and slides by using mouse or fingers. Requires fullpage.js >= 3.0.1. Possible values are:

    • true: enables the feature.
    • false: disables the feature.
    • vertical: enables the feature only vertically.
    • horizontal: enables the feature only horizontally.
    • fingersonly: enables the feature for touch devices only.
    • mouseonly: enables the feature for desktop devices only (mouse and trackpad).
  • offsetSections: (default false)Extension of fullpage.js. Provides a way to use non full screen sections based on percentage. Ideal to show visitors there's more content in the site by showing part of the next or previous section. Requires fullPage.js >= 3.0.1. To define the percentage of each section the attribute data-percentage must be used. The centering of the section in the viewport can be determined by using a boolean value in the attribute data-centered (default to true if not specified). For example:

    <div class="section" data-percentage="80" data-centered="true">
  • resetSliders: (default false). Extension of fullpage.js. Defines whether or not to reset every slider after leaving its section. Requires fullpage.js >= 3.0.1.

  • fadingEffect: (default false). Extension of fullpage.js. Defines whether to use a fading effect or not instead of the default scrolling one. Possible values are true, false, sections, slides. It can therefore be applied just vertically or horizontally, or to both at the time. It can only be used when using: autoScrolling:true. Requires fullpage.js >= 3.0.1.

  • animateAnchor: (default true) Defines whether the load of the site when given an anchor (#) will scroll with animation to its destination or will directly load on the given section.

  • recordHistory: (default true) Defines whether to push the state of the site to the browser's history. When set to true each section/slide of the site will act as a new page and the back and forward buttons of the browser will scroll the sections/slides to reach the previous or next state of the site. When set to false, the URL will keep changing but will have no effect on the browser's history. This option is automatically turned off when using autoScrolling:false.

  • menu: (default false) A selector can be used to specify the menu to link with the sections. This way the scrolling of the sections will activate the corresponding element in the menu using the class active. This won't generate a menu but will just add the active class to the element in the given menu with the corresponding anchor links. In order to link the elements of the menu with the sections, an HTML 5 data-tag (data-menuanchor) will be needed to use with the same anchor links as used within the sections. Example:

<ul id="myMenu">
	<li data-menuanchor="firstPage" class="active"><a href="#firstPage">First section</a></li>
	<li data-menuanchor="secondPage"><a href="#secondPage">Second section</a></li>
	<li data-menuanchor="thirdPage"><a href="#thirdPage">Third section</a></li>
	<li data-menuanchor="fourthPage"><a href="#fourthPage">Fourth section</a></li>
</ul>
new fullpage('#fullpage', {
	anchors: ['firstPage', 'secondPage', 'thirdPage', 'fourthPage', 'lastPage'],
	menu: '#myMenu'
});

Note: the menu element should be placed outside the fullpage wrapper in order to avoid problem when using css3:true. Otherwise it will be appended to the body by the plugin itself.

  • navigation: (default false) If set to true, it will show a navigation bar made up of small circles.

  • navigationPosition: (default none) It can be set to left or right and defines which position the navigation bar will be shown (if using one).

  • navigationTooltips: (default []) Defines the tooltips to show for the navigation circles in case they are being used. Example: navigationTooltips: ['firstSlide', 'secondSlide']. You can also define them by using the attribute data-tooltip in each section if you prefer.

  • showActiveTooltip: (default false) Shows a persistent tooltip for the actively viewed section in the vertical navigation.

  • slidesNavigation: (default false) If set to true it will show a navigation bar made up of small circles for each landscape slider on the site.

  • slidesNavPosition: (default bottom) Defines the position for the landscape navigation bar for sliders. Admits top and bottom as values. You may want to modify the CSS styles to determine the distance from the top or bottom as well as any other style such as color.

  • scrollOverflow: (default false) defines whether or not to create a scroll for the section/slide in case its content is bigger than the height of it. When set to true, your content will be wrapped by the plugin. Consider using delegation or load your other scripts in the afterRender callback. In case of setting it to true, it requires the vendor library scrolloverflow.min.js. This file has to be loaded before the fullPage.js plugin, but after jQuery ( in case of using it). For example:

<script type="text/javascript" src="vendors/scrolloverflow.min.js"></script>
<script type="text/javascript" src="fullpage.js"></script>

In order to prevent fullpage.js from creating the scrollbar in certain sections or slides use the class fp-noscroll. For example: <div class="section fp-noscroll">

You can also prevent scrolloverflow from getting applied on responsive mode when using fp-auto-height-responsive in the section element.

  • scrollOverflowReset: (default false) Extension of fullpage.js. When set to true it scrolls up the content of the section/slide with scroll bar when leaving to another vertical section. This way the section/slide will always show the start of its content even when scrolling from a section under it.

  • scrollOverflowOptions: when using scrollOverflow:true fullpage.js will make use of a forked and modified version of iScroll.js library. You can customize the scrolling behaviour by providing fullpage.js with the iScroll.js options you want to use. Check its documentation for more info.

  • sectionSelector: (default .section) Defines the Javascript selector used for the plugin sections. It might need to be changed sometimes to avoid problem with other plugins using the same selectors as fullpage.js.

  • slideSelector: (default .slide) Defines the Javascript selector used for the plugin slides. It might need to be changed sometimes to avoid problem with other plugins using the same selectors as fullpage.js.

  • responsiveWidth: (default 0) A normal scroll (autoScrolling:false) will be used under the defined width in pixels. A class fp-responsive is added to the body tag in case the user wants to use it for their own responsive CSS. For example, if set to 900, whenever the browser's width is less than 900 the plugin will scroll like a normal site.

  • responsiveHeight: (default 0) A normal scroll (autoScrolling:false) will be used under the defined height in pixels. A class fp-responsive is added to the body tag in case the user wants to use it for their own responsive CSS. For example, if set to 900, whenever the browser's height is less than 900 the plugin will scroll like a normal site.

  • responsiveSlides: (default false) Extension of fullpage.js. When set to true slides will be turned into vertical sections when responsive mode is fired. (by using the responsiveWidth or responsiveHeight options detailed above). Requires fullpage.js >= 3.0.1.

  • parallax: (default false) Extension of fullpage.js. Defines whether or not to use the parallax backgrounds effects on sections / slides. Read more about how to apply the parallax option.

  • parallaxOptions: (default: { type: 'reveal', percentage: 62, property: 'translate'}). Allows to configure the parameters for the parallax backgrounds effect when using the option parallax:true. Read more about how to apply the parallax option.

  • dropEffect (default false) Extension of fullpage.js. Defines whether or not to use the drop effect on sections / slides. Read more about how to apply the the drop effect option.

  • dropEffectOptions: (default: { speed: 2300, color: '#F82F4D', zIndex: 9999}). Allows to configure the parameters for the drop effect when using the option dropEffect:true.Read more about how to apply the the drop effect option.

  • cards: (default false) Extension of fullpage.js. Defines whether or not to use the cards effect on sections/slides. Read more about how to apply the cards option.

  • cardsOptions: (default: { perspective: 100, fadeContent: true, fadeBackground: true}). Allows you to configure the parameters for the cards effect when using the option cards:true. Read more about how to apply the cards option.

  • lazyLoading: (default true) Lazy loading is active by default which means it will lazy load any media element containing the attribute data-src as detailed in the Lazy Loading docs . If you want to use any other lazy loading library you can disable this fullpage.js feature.

Methods

You can see them in action here

getActiveSection()

Demo Gets an Object (type Section) containing the active section and its properties.

fullpage_api.getActiveSection();

getActiveSlide()

Demo Gets an Object (type Slide) containing the active slide and its properties.

fullpage_api.getActiveSlide();

moveSectionUp()

Demo Scrolls one section up:

fullpage_api.moveSectionUp();

moveSectionDown()

Demo Scrolls one section down:

fullpage_api.moveSectionDown();

moveTo(section, slide)

Demo Scrolls the page to the given section and slide. The first section will have the index 1 whilst the first slide, the visible one by default, will have index 0.

/*Scrolling to the section with the anchor link `firstSlide` and to the 2nd Slide */
fullpage_api.moveTo('firstSlide', 2);
//Scrolling to the 3rd section (with index 3) in the site
fullpage_api.moveTo(3, 0);

//Which is the same as
fullpage_api.moveTo(3);

silentMoveTo(section, slide)

Demo Exactly the same as moveTo but in this case it performs the scroll without animation. A direct jump to the destination.

/*Scrolling to the section with the anchor link `firstSlide` and to the 2nd Slide */
fullpage_api.silentMoveTo('firstSlide', 2);

moveSlideRight()

Demo Scrolls the horizontal slider of the current section to the next slide:

fullpage_api.moveSlideRight();

moveSlideLeft()

Demo Scrolls the horizontal slider of the current section to the previous slide:

fullpage_api.moveSlideLeft();

setAutoScrolling(boolean)

Demo Sets the scrolling configuration in real time. Defines the way the page scrolling behaves. If it is set to true, it will use the "automatic" scrolling, otherwise, it will use the "manual" or "normal" scrolling of the site.

fullpage_api.setAutoScrolling(false);

setFitToSection(boolean)

Demo Sets the value for the option fitToSection determining whether to fit the section in the screen or not.

fullpage_api.setFitToSection(false);

fitToSection()

Demo Scrolls to the nearest active section fitting it in the viewport.

fullpage_api.fitToSection();

setLockAnchors(boolean)

Demo Sets the value for the option lockAnchors determining whether anchors will have any effect in the URL or not.

fullpage_api.setLockAnchors(false);

setAllowScrolling(boolean, [directions])

Demo Adds or remove the possibility of scrolling through sections/slides by using the mouse wheel/trackpad or touch gestures (which is active by default). Note this won't disable the keyboard scrolling. You would need to use setKeyboardScrolling for it.

  • directions: (optional parameter) Admitted values: all, up, down, left, right or a combination of them separated by commas like down, right. It defines the direction for which the scrolling will be enabled or disabled.
//disabling scrolling
fullpage_api.setAllowScrolling(false);

//disabling scrolling down
fullpage_api.setAllowScrolling(false, 'down');

//disabling scrolling down and right
fullpage_api.setAllowScrolling(false, 'down, right');

setKeyboardScrolling(boolean, [directions])

Demo Adds or remove the possibility of scrolling through sections by using the keyboard (which is active by default).

  • directions: (optional parameter) Admitted values: all, up, down, left, right or a combination of them separated by commas like down, right. It defines the direction for which the scrolling will be enabled or disabled.
//disabling all keyboard scrolling
fullpage_api.setKeyboardScrolling(false);

//disabling keyboard scrolling down
fullpage_api.setKeyboardScrolling(false, 'down');

//disabling keyboard scrolling down and right
fullpage_api.setKeyboardScrolling(false, 'down, right');

setRecordHistory(boolean)

Demo Defines whether to record the history for each hash change in the URL.

fullpage_api.setRecordHistory(false);

setScrollingSpeed(milliseconds)

Demo Defines the scrolling speed in milliseconds.

fullpage_api.setScrollingSpeed(700);

destroy(type)

Demo Destroys the plugin events and optionally its HTML markup and styles. Ideal to use when using AJAX to load content.

  • type: (optional parameter) can be empty or all. If all is passed, the HTML markup and styles used by fullpage.js will be removed. This way the original HTML markup, the one used before any plugin modification is made, will be maintained.
//destroying all Javascript events created by fullPage.js (scrolls, hashchange in the URL...)
fullpage_api.destroy();

//destroying all Javascript events and any modification done by fullPage.js over your original HTML markup.
fullpage_api.destroy('all');

reBuild()

Updates the DOM structure to fit the new window size or its contents. Ideal to use in combination with AJAX calls or external changes in the DOM structure of the site, specially when using scrollOverflow:true.

fullpage_api.reBuild();

setResponsive(boolean)

Demo Sets the responsive mode of the page. When set to true the autoScrolling will be turned off and the result will be exactly the same one as when the responsiveWidth or responsiveHeight options get fired.

fullpage_api.setResponsive(true);

responsiveSlides.toSections()

Extension of fullpage.js. Requires fullpage.js >= 3.0.1. Turns horizontal slides into vertical sections.

fullpage_api.responsiveSlides.toSections();

responsiveSlides.toSlides()

Extension of fullpage.js. Requires fullpage.js >= 3.0.1. Turns back the original slides (now converted into vertical sections) into horizontal slides again.

fullpage_api.responsiveSlides.toSlides();

Callbacks

Demo You can see them in action here.

Some callbacks, such as onLeave will contain Object type of parameters containing the following properties:

  • anchor: (String) item's anchor.
  • index: (Number) item's index.
  • item: (DOM element) item element.
  • isFirst: (Boolean) determines if the item is the first child.
  • isLast: (Boolean) determines if the item is the last child.

afterLoad (origin, destination, direction)

Callback fired once the sections have been loaded, after the scrolling has ended. Parameters:

  • origin: (Object) section of origin.
  • destination: (Object) destination section.
  • direction: (String) it will take the values up or down depending on the scrolling direction.

Example:

new fullpage('#fullpage', {
	anchors: ['firstPage', 'secondPage', 'thirdPage', 'fourthPage', 'lastPage'],

	afterLoad: function(origin, destination, direction){
		var loadedSection = this;

		//using index
		if(origin.index == 2){
			alert("Section 3 ended loading");
		}

		//using anchorLink
		if(origin.anchor == 'secondSlide'){
			alert("Section 2 ended loading");
		}
	}
});

onLeave (origin, destination, direction)

This callback is fired once the user leaves a section, in the transition to the new section. Returning false will cancel the move before it takes place.

Parameters:

  • origin: (Object) section of origin.
  • destination: (Object) destination section.
  • direction: (String) it will take the values up or down depending on the scrolling direction.

Example:

new fullpage('#fullpage', {
	onLeave: function(origin, destination, direction){
		var leavingSection = this;

		//after leaving section 2
		if(origin.index == 1 && direction =='down'){
			alert("Going to section 3!");
		}

		else if(origin.index == 1 && direction == 'up'){
			alert("Going to section 1!");
		}
	}
});

Cancelling the scroll before it takes place

You can cancel the scroll by returning false on the onLeave callback:

new fullpage('#fullpage', {
	onLeave: function(origin, destination, direction){
		//it won't scroll if the destination is the 3rd section
		if(destination.index == 2){
			return false;
		}
	}
});

afterRender()

This callback is fired just after the structure of the page is generated. This is the callback you want to use to initialize other plugins or fire any code which requires the document to be ready (as this plugin modifies the DOM to create the resulting structure). See FAQs for more info.

Example:

new fullpage('#fullpage', {
	afterRender: function(){
		var pluginContainer = this;
		alert("The resulting DOM structure is ready");
	}
});

afterResize(width, height)

This callback is fired after resizing the browser's window. Just after the sections are resized.

Parameters:

  • width: (Number) window's width.
  • height: (Number) window's height.

Example:

new fullpage('#fullpage', {
	afterResize: function(width, height){
		var fullpageContainer = this;
		alert("The sections have finished resizing");
	}
});

afterReBuild()

This callback is fired after manually re-building fullpage.js by calling fullpage_api.reBuild().

Example:

new fullpage('#fullpage', {
	afterReBuild: function(){
		console.log("fullPage.js has manually being re-builded");
	}
});

afterResponsive(isResponsive)

This callback is fired after fullpage.js changes from normal to responsive mode or from responsive mode to normal mode.

Parameters:

  • isResponsive: (Boolean) determines if it enters into responsive mode (true) or goes back to normal mode (false).

Example:

new fullpage('#fullpage', {
	afterResponsive: function(isResponsive){
		alert("Is responsive: " + isResponsive);
	}
});

afterSlideLoad (section, origin, destination, direction)

Callback fired once the slide of a section have been loaded, after the scrolling has ended.

Parameters:

  • section: (Object) active vertical section.
  • origin: (Object) horizontal slide of origin.
  • destination: (Object) destination horizontal slide.
  • direction: (String) right or left depending on the scrolling direction.

Example:

new fullpage('#fullpage', {
	anchors: ['firstPage', 'secondPage', 'thirdPage', 'fourthPage', 'lastPage'],

	afterSlideLoad: function( section, origin, destination, direction){
		var loadedSlide = this;

		//first slide of the second section
		if(section.anchor == 'secondPage' && destination.index == 1){
			alert("First slide loaded");
		}

		//second slide of the second section (supposing #secondSlide is the
		//anchor for the second slide)
		if(section.index == 1 && destination.anchor == 'secondSlide'){
			alert("Second slide loaded");
		}
	}
});

onSlideLeave (section, origin, destination, direction)

This callback is fired once the user leaves an slide to go to another, in the transition to the new slide. Returning false will cancel the move before it takes place.

Parameters:

  • section: (Object) active vertical section.
  • origin: (Object) horizontal slide of origin.
  • destination: (Object) destination horizontal slide.
  • direction: (String) right or left depending on the scrolling direction.

Example:

new fullpage('#fullpage', {
	onSlideLeave: function( section, origin, destination, direction){
		var leavingSlide = this;

		//leaving the first slide of the 2nd Section to the right
		if(section.index == 1 && origin.index == 0 && direction == 'right'){
			alert("Leaving the fist slide!!");
		}

		//leaving the 3rd slide of the 2nd Section to the left
		if(section.index == 1 && origin.index == 2 && direction == 'left'){
			alert("Going to slide 2! ");
		}
	}
});

Cancelling a move before it takes place

You can cancel a move by returning false on the onSlideLeave callback. Same as when canceling a movement with onLeave.

Reporting issues

  1. Please, look for your issue before asking using the github issues search.
  2. Make sure you use the latest fullpage.js version. No support is provided for older versions.
  3. Use the the Github Issues forum to create issues.
  4. An isolated reproduction of the issue will be required. Make use of jsfiddle or codepen for it if possible.

Contributing to fullpage.js

Please see Contributing to fullpage.js

Changelog

To see the list of recent changes, see Releases section.

Build tasks

Want to build fullpage.js distribution files? Please see Build Tasks

Resources

Who is using fullPage.js

If you want your page to be listed here, please contact me with the URL.

Google Coca-cola eBay BBC Sony

Vodafone British Airways McDonalds EA Vogue Mi

Mercedes sym Bugatti eDarling Ubisoft

You can find another list here.

Donations

Donations would be more than welcome :)

Donate

Sponsors

Become a sponsor and get your logo on our README on Github with a link to your site. [Become a sponsor] | [Become a patreon]

Stackpath Browserstack CodePen CodeFirst

People

Comments
  • Avoid accidental scrolling when reading content in the bottom of the slide when using scrollOverflow:true

    Avoid accidental scrolling when reading content in the bottom of the slide when using scrollOverflow:true

    I am having one interesting behavior where some of the slides have content which is positioned at or near the bottom of the pages. So, on smaller screens where the content can't be shown all at once, when the user scrolls down to see the content, he or she might overscroll (via mouse or touch pad) and instead of just scrolling to see the content trigger the new page slide in as well, so the user can't read the content and has to go back.

    One solution might be too change the content structure and add some padding or empty space below the actual content, but that seems like crude solution.

    Is there a way to solve this so in the initial scroll, when the user is actually scrolling the page which has height larger than the screen/window height, doesn't trigger the scroll event?

    Thanks

    bug enhancement Help needed Might not be possible fixed on dev 
    opened by elahmo 92
  • Orientation change on somet tablets

    Orientation change on somet tablets

    On the tablet websites do not display and do not scale well. In portrait orientation shows more than one section, while in landscape orientation section is cut off. On my 8 inch tablet problem occurs on all browsers except Chrome on another 7-inch tablet, the problem also appears on Chromie. If you refresh the page, the error disappears, but when you change the orientation back again.

    bug 
    opened by Rabauken 66
  • Making touch scroll work on Windows Phone 8

    Making touch scroll work on Windows Phone 8

    I have been able to make touch scrolling work in IE on my Windows Phone 8 phone.

    I added this to the css:

      #superContainer {
        -ms-touch-action: none;
     }
    

    In jquery.fullPage.js, I replaced lines 340 341 with:

                        if (event.type=='MSPointerMove'){
                            touchEndY = e.pageY;
                            touchEndX = e.pageX;
                        }
                        else {
                            touchEndY = e.touches[0].pageY;
                            touchEndX = e.touches[0].pageX;
                        }
    

    and, similarly, I replaced lines 398 399 with:

                        if (event.type=='MSPointerDown'){
                            touchStartY = e.pageY;
                            touchStartX = e.pageX;
    
                        }
                        else {
                            touchStartY = e.touches[0].pageY;
                            touchStartX = e.touches[0].pageX;
                        }
    
    opened by philrees 54
  • Chrome 44.0 issue

    Chrome 44.0 issue

    Have been building a site using fullPage and everything was working great until today (Chrome 44.0 was released yesterday). Now, with autoScrolling enabled (the default behaviour) it appears to jump to the first section each time i scroll (using the mouse) and scrolls through all sections until it reaches the 'next' section. It's even happening on the fullPage demo page.

    bug Help needed 
    opened by gwixted 52
  • Normal scrolling after one section

    Normal scrolling after one section

    Hi, I have a scrolling vertical section in 100% height of viewport for each section. Under last section i have a footer. I would set autoScrolling to false when i'm in last section because i need to set normal scrolling behaviour and then, in direction up, re-set autoScrolling to true.

    My code:

      var actualIndexSlide;
      var totalSlides = $('main > section.section').length;
      $('#main').fullpage({
        // autoScrolling: true,
        css3: true,
        verticalCentered: false,
        touchSensitivity: 15,
        easing: 'easeInCirc',
        normalScrollElements: '.fd-footer',
        resize: false,
        scrollingSpeed: 700,
    
        afterRender: function(){
          console.log("rendered");
          $('main > section').css('height','auto');
        },
    
        afterResize: function(){
          console.log("resize");
          $('main > section').css('height','auto');
        },
    
        afterLoad: function(anchor, index){
          actualIndexSlide = index;
          // console.log("after load | anchor:"+anchor+" | index: "+index);
          if(actualIndexSlide == totalSlides) {
            // $.fn.fullpage.scrollOverflow(false);
            $.fn.fullpage.setAutoScrolling(false);
          }
        },
    
        afterSlideLoad: function(anchorLink, index, slideAnchor, slideIndex){
        console.log("hereeee");
        },
    
        onLeave: function(index, newIndex, direction){
          console.log("nuova "+newIndex);
          console.log(index+"-"+totalSlides);
          console.log(direction);
          if(direction == "up" && index == totalSlides) {
            // $.fn.fullpage.moveSectionUp();
            $.fn.fullpage.moveTo(newIndex);
            setTimeout(function() {
              $.fn.fullpage.setAutoScrolling(true);
            }, 1300);
          }
        }
    
      });
    

    When i'm coming from last slide in up direction to second-to-last i have a flickering. I have 2 problem: afterSlideLoad not firing, never! And a blank page in google chrome on MAC.

    Any solutions? Thanks and sorry for my english! :)

    question fixed on dev 
    opened by agaletta 44
  • iOS 8.1 Mobile Auto Scrolling Off

    iOS 8.1 Mobile Auto Scrolling Off

    Hi, great plugin, thanks for all your work on it.

    I've noticed that ever since I've upgraded to iOS 8.1, there are still remnants of auto scrolling on the actual iPhone device when scrolling through the page. For instance, try the following steps:

    1. Go to your demo page - http://alvarotrigo.com/fullPage - on iPhone/Safari
    2. Open up web inspector
    3. Turn auto scrolling off... $.fn.fullpage.setAutoScrolling(false)
    4. Scroll up and down

    You should notice that the page jumps around as you scroll, when you really should expect the page to scroll smoothly.

    I'm going to investigate this in the source code, but I was wondering if you can look to and if you had any ideas off the top of your head.

    Thanks!

    bug 
    opened by rajenms 43
  • Demo issue

    Demo issue

    when using my scroll wheel (magic mouse) on the demo (http://alvarotrigo.com/fullPage/), the pages scroll jumps too far. For example, when I am on the first page, and scroll down to move to the second, I actually end up on the third. Make sense..? It seems to be too sensitive.

    opened by mrmartineau 40
  • “scrollBar:true” impacts performance/FPS • fixed/sticky elements inside “fullpage” wrapper

    “scrollBar:true” impacts performance/FPS • fixed/sticky elements inside “fullpage” wrapper

    Hi guys!

    I’m using Webflow and creating a website for a client with FullPage.js.

    I just wanted to ask why “scrollBar: true” impacts performance so much? FPS drops quite substantially. I’ve checked other websites with “scrollBar: true” like the demo one by Alvaro and another one that I’ll mention below.

    That being said, the website is so smooth without “scrollBar: true”.

    Is there a fix for the performance issues? Sadly, “position: fixed” doesn’t work inside “fullpage” wrapper without “scrollBar: true”. I needed it to create an animation.

    Basically, I want the same “sticky” effect as in the “second” section of this website (made in Webflow too). I’m really scratching my head here trying to understand how to create it :(

    Reproduction required 
    opened by GeorgyDesign 38
  • "Tab" key = bug

    Hello, I discovered a bug.

    If the website contains a link or a form when you press the "tab" key, the browser goes directly to the section concerned but the navigation is completely broken.

    enhancement Help needed Might not be possible fixed on dev 
    opened by meneldil 38
  • Add 'scrollOverflow:false' while responsive.

    Add 'scrollOverflow:false' while responsive.

    I would like to use fullPage.js and it's autoScrolling feature on my site but there's one thing making me not using it.

    When using 'responsive: value' the 'autoScrolling' feature is being turned off. The problem is that the 'scrollOverflow' feature remains unchanged from original.

    Would it be possible to turn off 'scrollOverflow' when 'responsive: value' is triggered? The reason I would like to do that is because I don't want to scroll within the '.section' in responsive mode, I just want it to act normal just like as if 'scrollOverflow' was turned off.

    So basically; How do I turn off 'scrollOverflow' when 'responsive' is triggered? It's very much needed for my design and I think it could be helpful for other too.

    I would like fullPage.js with the features 'autoScrolling' and 'scrollOverflow' to be enabed above the responsive breakpoint. But when 'responsive' triggers I want 'autoScrolling' and 'scrollOverflow' turned off, both of them.

    Thanks in advance

    enhancement fixed on dev 
    opened by partynikko 37
  • Mobile Safari height wrong with address bar and tabs

    Mobile Safari height wrong with address bar and tabs

    The height of a section is not set correctly on iOS Safari. You may try this out in Xcode Simulator. For example on iPhone 7 Plus the height of the viewport (without toolbar) is 370px, but the fullpage.js height of a section(set by $(window).height()) is 414px which includes the toolbar(address bar).

    To show this i added a header and a footer which are positioned absolute (top:0 / bottom:0).

    Initial: bildschirmfoto 2016-11-17 um 18 40 15

    Using $(window).scrollTop(1000): bildschirmfoto 2016-11-17 um 18 40 34

    A solution would be to use window.innerHeight. Interestingly it gives 414px (height with toolbar) on start, but with a timeout of 50ms it gives 370px (correct height without toolbar):

    1. Replace all $(window).height() with window.innerHeight
    2. Add a timeOut:
    setTimeout(function () {
            $('.section').css('height', window.innerHeight + 'px');
            $(window).scrollTop(0);
        }, 50);
    
    1. Additionally we need to listen for window changes. For example on rotation sometimes the toolbar gets hidden. Or if the toolbar is hidden and we tap into top screen and the toolbar shows. Or when opening a new tab in iPhone Plus Landscape or on rotation:
    $(window).on('resize', function() {
            $(window).scrollTop(0);
            $('.section').css('height', window.innerHeight + 'px');
    
            // Additional timeOut for iPhone Plus in landscape with multiple tabs opened
            setTimeout(function() {
                $('.section').css('height', window.innerHeight + 'px');
                $(window).scrollTop(0);
            }, 400);
        });
    

    I added an additional timeOut within the on resize which only affects iPhone Plus with multiple tabs opened(tab bar visible). In this case again window.innerHeight is wrong until an amount of time. 400ms was the minimum i discovered.

    With this 3 changes the height stays always perfect.

    If not using the option verticalCentered: falsethe height changes needs to be done to .fp-tableCell, too.

    Reproduction required 
    opened by MickL 36
  • in mobile view navbar is not work

    in mobile view navbar is not work

    Hello dear,

    when I open my project in mobile that time nav bar is not work. nav bar is open but any section link is not work. Ex.=> I click navigation it open but in navigation i click on service, about etc. page is not open. but in laptop its work wonder please give any solution

    opened by Nehul50 0
  • How do I use a callback to tell me that I've scrolled outside of fullpage?

    How do I use a callback to tell me that I've scrolled outside of fullpage?

    Description

    I have tried "onleave", but it only seems to trigger if I am scrolling from one section to another. I need a callback to trigger if you leave the last slide and scroll past all the sections into the footer.

    Here is a demo: https://codepen.io/kylerumble/pen/zYLxexB

    You can see that the scrollbar is set to true. And I'd like to be able to know when the page is scrolled outside of the last slide.

    enhancement 
    opened by iamcanadian1973 1
  • Purchased license not valid anymore

    Purchased license not valid anymore

    Description

    Purchased license (fullPage.js Commercial Hobby License) on Apr 30, 2021 and not valid now for version 3.1.2.

    Reached at support but forwarded me here to open an issue.

    Link to isolated reproduction with no external CSS / JS

    Demo on https://www.bakucitycircuit.com/en

    Steps to reproduce it

    1. Go to demo link https://www.bakucitycircuit.com/en
    2. Check console

    Versions

    fullPage 3.1.2, Google Chrome Version 108.0.5359.124

    question 
    opened by elnurxf 2
  • fp-auto-height and scrollOverflow not working together

    fp-auto-height and scrollOverflow not working together

    Description

    fullPage.js won't generate scrollable elements when using the class fp-auto-height in a section together with the fullpage.js option scrollOverflow: true.

    On desktop it shows a section smaller than the viewport. On mobile, when the height is small enough, the section will need to create a scrollbar inside that section if no responsive option is used and autoScrolling is on. However, this won't happen.

    Link to isolated reproduction with no external CSS / JS

    https://codepen.io/alvarotrigo/pen/WNyVbKr

    Steps to reproduce it

    1. Go to: https://codepen.io/alvarotrigo/pen/WNyVbKr
    2. Resize down the viewport size to a max of 588px height.
    3. See how the last section doesn't contain scrollable content (when it needs it)

    Versions

    fullPage.js 4.0.15

    bug fixed on dev 
    opened by alvarotrigo 1
  • Have trouble with using normal scroll sections before auto scrolling sections.

    Have trouble with using normal scroll sections before auto scrolling sections.

    Hi, thanks for creating such a great plugin. I really love to use this but I have trouble with using normalScrollElements. image As you can see, above screenshot first section has scrollable-content and it has 3 subsections.

    Here's my javascript code for Fullpage

    new fullpage("#fullpage", {
          licenseKey: 'xxx',
          navigation: false,
          scrollBar: true,
          scrollingSpeed: 1000,
          scrollOverflow: true,
          sectionSelector: 'section',
          normalScrollElements: '.scrollable-content',
          credits: false,
          responsiveWidth: 800
        });
    

    I tried to made normal scrolling elements from this example. https://codepen.io/alvarotrigo/pen/RmVazM

    Reproduction required 
    opened by MasterDev333 1
Releases(4.0.15)
  • 4.0.15(Nov 22, 2022)

    • Fixed bug: Offset sections extensions not working as expected #4491
    • Fixed bug: scrollOverflow: true + scrollBar: true causes touch events issues #4490
    • Fixed bug: Safari applies the wrong offset on scroll to anchor & sometimes on scroll #4484
    • Documentation: updated gzip size & improved style #4488 thanks to @cloydlau
    Source code(tar.gz)
    Source code(zip)
  • 4.0.14(Nov 11, 2022)

    • Fixed bug: auto-height sections ignored min-height #4471
    • Fixed bug changes on ScrollOverflow content trigger scroll page #4479
    • Fixed bug: Offset Sections extension had issues on page load
    • Fixed bug: Responsive Slides showed a console error
    • Fixed bug: removed console message on extensions file
    • Documentation: updating bakers.md
    • Enhancement: allowing extra domains for activations
    Source code(tar.gz)
    Source code(zip)
  • 4.0.12(Oct 24, 2022)

    • Fixed bug: Loading page with anchors shows wrong section/slide when using scrollOverflow #4464
    • Fixed bug: auto-height sections ignored min-height #4471
    • Fixed bug: slides not sliding after resizeEvent triggered on input change #4466
    • Fixed bug: fp-auto-heightt section behaves as full-height when using autoScrolling: false #4467
    • Fixed bug: GPLv3 license was giving error #4463
    • Fixed bug: scrollBar: true didn't prevent touch scroll sometimes
    • Fixed bug: Responsive Slides extension was not working properly
    • Fixed bug: fp-auto-height sections ignored min-height #4471
    • Enhancement: removing commented-out styles
    • Enhancement: refactoring event strings to properties
    • Documentation: fixed indenting on lists
    • Documentation: removing unnecessary text
    • Documentation: updating links to secure links with https
    • Documentation: removing websites without fullpage.js
    Source code(tar.gz)
    Source code(zip)
  • 4.0.11(Sep 8, 2022)

    • Fixed bug: Section Overflows with scrollBar:true & large content #4447
    • Fixed bug: keyboard navigation on scrollOverflow section didn't work until clicking on it
    • FIxed bug: Keyboard scrolling not working on responsive mode #4452
    • Fixed bug: scroll event not being captured on window object with fitToSection: true
    • Fixed bug: Fast click on nav bullets caused unwanted glitches
    • Fixed bug: scrolling issues iOS + scrollOverflow + horizontal slides #4454
    • Fixed bug: scrollable content wasn't able to have background #4448 #4447
    • Enhancement: dynamically content changes can automatically become scrollable with scrollOverflow
    • Enhancement: tabbing didn't force scroll #4453
    • Enhancement: reverting fitToSection from CSS Snaps to custom JS
    • Fixed bug: fp-noscroll didn't show the top of content #4430
    • Documentation: fixed minor grammar errors thanks to @BossElijah
    • Documentation: updating the link to the migration guide
    • Documentation: added Brazilian language thanks to @guilherssousa #4417
    Source code(tar.gz)
    Source code(zip)
  • 4.0.10(Aug 7, 2022)

    • Fixed bug: auto-height + scrollOverflow #4435
    • Fixed bug: menu doesn't work when I use responsiveWidth #4432
    • Fixed bug: white screen when clicking input on Android #4420
    • Fixed bug: beforeLeave not triggered on scroll on page load #4418
    • Fixed bug: scrollOverflow + parallax didn't work
    • Fixed bug: fp-noscroll not working #4430
    • Examples: Improved callbacks example
    • Documentation: fixing codepen link
    • Enhancement: improved error message for licenseKey
    Source code(tar.gz)
    Source code(zip)
  • 4.0.9(May 30, 2022)

    • Fixed bug: Fullpage stops scrolling while swiping before the movement ends #4397
    • Fixed bug: scrollBar causes no scroll transition scrolling back #4398
    Source code(tar.gz)
    Source code(zip)
  • 4.0.8(May 20, 2022)

    • Fixed bug: fullpage.js didn't work on Safari < 13 #4390
    • Fixed bug: scrollOverflow + floating distances prevented it from moving to next section #4391
    • Fixing bug on input focus on Android #4393
    • Enhancement: improved scrollBar: true performance with requestAnimationFrame #4344
    • Fixed bug: fixing problem with react-fullpage & gatsby on redirect https://github.com/alvarotrigo/react-fullpage/issues/325
    • Fixed bug: swipe didn't work on touchscreen computers
    Source code(tar.gz)
    Source code(zip)
  • 4.0.7(May 9, 2022)

    • Fixed bug: scrollOverflowReset not working as expected #4388
    • Fixed bug: scrollBar & fp-auto-height & fitToSection adjusting to the wrong section #4380
    • Fixed bug: touchScreen swipe with fitToSection:false & scrollBar:true - always scrolls down #4376
    • Fixed bug: spacebar not working in form fields #4373
    • Fixed bug: invalid licenseKey was breaking site #4368
    • Fixed bug: waterEffect + dragAndMove minified options issues
    • Documentation: incorrect data on "this" for callbacks #4337
    Source code(tar.gz)
    Source code(zip)
  • 4.0.6(Apr 19, 2022)

  • 4.0.5(Apr 12, 2022)

  • 4.0.4(Apr 11, 2022)

  • 4.0.3(Apr 11, 2022)

  • 4.0.2(Apr 11, 2022)

    • Enhancement: customizable navigating arrows
    • Enhancement: fullPage.js ignores hidden sections on responsive #2941 #2098
    • Enhancement: normal scroll after fullpage #614 #840 #3205
    • Enhancement: new option observer. fullpage.js reacts to DOM changes. #1926
    • Enhancement: new option scrollOverflowMacStyle
    • Enhancement: new option controlArrowsHTML for custom arrows #4267 #4179 #1382 #635 #351
    • Enhancement: added beforeLeave callback that allows preventing scroll #1262 #787 #3393 #340 #117 #3085 #1239 #364
    • Enhancement: horizontal navigation bullets will get instant response on slide #4234 #3240
    • Enhancement: added trigger param in all callbacks #4110
    • Enhancement: added onScrollOverflow callback to track Y position #4061 #3386
    • Enhancement: added getScrollY and getScrollX methods to track positions #4043
    • Enhancement: scrollable sections can now be scrolled programmatically #3779
    • Enhancement: verticalCentered will now use flexbox and won't wrap the content
    • Enhancement: sections will no longer use fixed height in px in favour of 100vh
    • Enhancement: fitToSection will now use native CSS snaps behaviour
    • Enhancement: scrollOverflowReset will now admit slides and section values.
    • Enhancement: changed the way extensions activation works
    • Enhancement: changed the way fullPage.js license works
    • Enhancement: new option credits
    • Fixed bug: scrollbar:true caused flickering. #4345
    • Fixed bug: scrollOverflow accidental scrolling when reading sections' bottom #941
    • Fixed bug: scrollOverflow sections were not scrollable by arrow keys #1065 #4205 #3652
    • Fixed bug: scrollOverflow prevented Vimeo video turn fullscreen #4104
    • Fixed bug: scrollOverflow prevented YouTube video turn fullscreen #2804
    • Fixed bug: scrollOverflow prevented the use of audio controls in IE #2139
    • Fixed bug: scrollOverflow prevented inputs clicks on mobile #3414 #2837
    • Fixed bug: navigation anchors & scrollBar didn't allow fast clicks on menu #1509
    • Fixed bug: wrong height of section on IOS 13 and below #4072 #2637
    • Fixed bug: strange bottom rectangle on chrome android #4073 #4085
    • Documentation: incorrect value for "this" for callbacks #4337 #4050
    • Documentation: added SECURITY.md file #4328
    • Documentation: removed possible confusion regarding initialisation #4256
    • Documentation: improved russian docs #4262
    • Removed: v2compatible option
    • Removed: scrolloverflow.min.js dependency
    • Removed: fitToSectionDelayoption
    • Removed: scrollOverflowOptions option
    • Removed: IE 9 compatibility
    Source code(tar.gz)
    Source code(zip)
  • 3.1.2(Jun 24, 2021)

  • 3.1.1(May 4, 2021)

  • 3.1.0(Feb 18, 2021)

    • New Drop Effect extension and new options dropEffect and dropEffectOptions
    • Fixed bug: Data anchors in URL not updating on scroll #4162
    • Fixed bug: On responsive mode callbacks are not firing #4082
    • Fixed bug: anchors not updating when using option `sectionSelector #4010
    • Fixed bug: dragAndMove caused slow transition on goinb back to 1st slide on 1st section
    • Documentation: Removed 2 invalid links from documentation and improved part of other #4042 thanks to @ivan-balanar
    • Gulp: created gulp task to automate version variable update
    • Gulp: updating default task
    • Gulp: updating readme.md version number
    Source code(tar.gz)
    Source code(zip)
  • 3.0.9(Jul 7, 2020)

    • Fixed bug: normalScrollElements + scrollOverflow when no scrollbar created
    • Fixed bug: setting isWindowFocused back to true after focus events to allow scrolling again #3832 thanks to @jbez
    • Fixed bug: scrollOverflow not work in Microsoft Edge #3840
    • Fixed bug: Lazy load ignores fp-auto-height-reponsive #3944
    • Fixed bug: error with normalScrollElements and mouse leave to debug console. #3931 #3973 thanks to @AlekseiKrivo
    • Fixed bug: dragAndMove slow move back to 1st slide within section #3962
    • Fixed bug: fixing screen readers info in horizontal slides bullets #3898
    • Fixed bug: applying only a few anchors was placing them in the wrong sections #3983
    • Fixed bug: wrong active section when switching landscape to portrait when using responsiveHeight #3897
    • Fixed bug: added minimum transition laps when using a very fast scrolling speed #3826
    • Fixed bug: Responsive Slides extension was losing listeners attached to elements when switching modes #3819
    • Documentation: added French docs thanks to @MercureTony
    • Documentation: parallax specific for "slides" or "sections"
    • Documentation: clarifying that scrollBar is only for vertical sections
    • Documentation: removed chinese typo #3935
    • Documentation: added demo for bigSectionsDestination + clarified description #4002
    • Documentation: removing old links
    • Enhancement: vertical center navigation using 2D transform #3925 thanks to @alanalvarado
    Source code(tar.gz)
    Source code(zip)
  • 3.0.8(Nov 25, 2019)

    Fixed bug: normalScrollElement bug after clicking on the element #3808 Fixed bug: normalScroll + fixed element didn't work well on firefox #3775 #3754 Fixed bug: overflow:scroll isn't scrollable inside scrollOverflow #3725 Documentation: clarifying the use of a single extension key option to use multiple domains. Documentation: improved Chinese docs #3708 #3710 thanks to @AnMokoto and @liufushihai Documentation: removed redundancy thanks to @haider-ilahi Examples: added React and Angular examples

    Source code(tar.gz)
    Source code(zip)
  • 3.0.7(Jul 10, 2019)

    • Fixed bug: scrollOverflow not working in mobile #3690
    • Fixed bug: vendor minified files were not up to date
    • Fixed bug: dist files were not up to date
    Source code(tar.gz)
    Source code(zip)
  • 3.0.6(Jul 10, 2019)

    • Fixed bug: facebook & instagram browser miscalculates page height #3675
    • Fixed bug: IOS 12 Progressive Web App Responsive resizing #3488
    • Fixed bug: OrientationChange breaks layout on Chrome mobile #3336
    • Fixed bug: Lazy loading fp-auto-height does not load all images in viewport #3647
    • Fixed bug: origin param in afterLoad call back is null #3671
    • Fixed bug: content gets hidden at the bottom when using lazyload:true and scrolloverflow:true #3621
    • Fixed bug: dragAndMove was not compatible with normalScrollElements
    • Fixed bug: scrollOverflow last scroll prevents to scroll to the bottom of a section #3527
    • Fixed bug: wrong navigation dot activated when using continuousVertical #3688 #2917
    • Fixed bug: normalScrollElements & fancybox not working as expected #3661
    • Fixed bug: scrollOerflow + verticalCentered + paddingTop #3609
    • Fixed bug: middle Mouse Scrolling is Broken when using autoScrolling:false #3684
    • Fixed bug: scrolloverflow IScroll is not defined when using bundler #3655 thanks to @gnuletik
    • Fixed bug: $(...).fullpage is not a function after destroy #3649
    • Fixed bug: Safari iOS - Vertical Align Bug #3636
    • Fixed bug: normalScrollElements & scrollBar:true & setAllowScrolling method not working together #3162
    • Enhancement: spacebar won't cause scroll on HTML videos and audios #1977
    • Documentation: added demo link for Autoplay- pause media
    • Documentation: added afterRebuild Documentation: added afterRebuild callback to the docs callback to the docs
    • Documentation: added link to Wordpress plugin for Gutenberg
    • Documentation: Clarifies section index starts at 1 and slide at 0 #3626 thanks to @SulphurDioxide
    • Documentation: adding normalScrollElements demo link alvarotrigo
    • Removed normalScrollElementTouchThreshold option
    • Tests: updated tests to match the new version
    Source code(tar.gz)
    Source code(zip)
  • 3.0.5(Apr 12, 2019)

    • Added new options cards and cardsOptions for the Cards extension
    • Fixed bug: scrollOverflow vendors file was not up to date and created errors #3525
    • Fixed bug: setAllowScrolling(false) was still preventing mouse actions on mobile #3520
    • Fixed bug: dragAndMove slowed down when sliding to 1st slide
    • Fixed bug: scrollOverflow tilting when reaching bottom #3415
    • Fixed bug: $.fn.fullpage methods not available in afterLoad #3510
    • Fixed bug: recordHistory not working with scrollBar:true #3566
    • Fixed bug: flickering error on Google Chrome 73 #3600
    • Fixed bug: scrollOverflow can't scroll if modal closed on mobile #3576 #3435
    • Fixed bug: enabling the use of multiple menu elements #3613 Thanks to @englishtom
    • Enhancement: getFullpageData as function #3588
    • Enhancement: added touchWrapper option
    • Documentation: removing link from who is using fulllPage
    • Documentation: clarify that extensions are only available for fullpage v3
    • Documentation: updating backers.md
    Source code(tar.gz)
    Source code(zip)
  • 3.0.4(Nov 29, 2018)

    • Fixed bug: data-anchor attributes stayed in DOM on destroy('all')
    • Fixed bug: scrollOverflow causing maximum call stack size exceeded in certain casesreact-fullpage/38
    • Fixed bug: initialisation fails with jQuery adapter using a class #3433
    • Fixed bug: loss attached events on unwrapping #3436 thanks to @Khusainov
    • Fixed bug: Uncaught ReferenceError: fullpage is not defined vue-fullpage.js/#60 thanks to @splex7
    • Fixed bug: destroy('all') showing error when scrollOverflow file present but not used
    • Fixed bug: direction is undefined in afterLoad Event #3480
    • Fixed bug: isLast never true in afterSlideLoad & onSlideLeave callbacks when having multiple sections with slides #3471 thanks to @i22tha
    • Fixed bug: setAllowScrolling not working in afterLoad #3490
    • Fixed bug: wrong sizes when using paddingTop & scrollOverflow & verticalCentered #3335 #3484
    • Fixed bug: Ajax jQuery stops working after resizing the screen two times. #3440
    • Fixed bug: normalScrollElements requires a 1st touch in touch screens #3481
    • Fixed bug: Fancybox with scroll doesn't work #3435 #3481
    • Fixed bug: OrientationChange on Slides breaks Layout on Chrome (mobile) #3336
    • Improved: now it is possible to use a menu without using anchors #2755
    • Improved: internal function deepExtend
    • Improved: removed jQuery dependency in package.json
    • Documentation: fixed broken link for iScroll docs #3489 thanks to @bott1222
    • Documentation: fixing broken link & format typos in different languages #3494 #3489
    • Documentation: fixing broken links to fp-auto-height-responsive demo #3483
    • Documentation: added a new sponsor: Codefirst
    • Documentation: added link to new Angular wrapper angular-fullpage.
    Source code(tar.gz)
    Source code(zip)
  • 3.0.3(Sep 26, 2018)

    • Fixed bug: vendors/easings.js file was not working as expected. Thanks to @bpmusicDE #3355
    • Fixed bug: it was not possible to tab to fixed elements #3144 #3408
    • Fixed bug: bullet navigation not working after destroy and reload #3413
    • Fixed bug: console error on tab with no focusable elements. Thanks @ArsalanDotMe #3364
    • Fixed bug: prevent focus on tabindex=-1 and hidden focusable elements
    • Fixed bug: showError was undefined in Query Adapter #3366. Thanks to @jmgiaever
    • Fixed bug: jquery & fullpage globals were undefined on react-fullpage.js when using jQuery
    • Fixed bug: fp-auto-height-responsive was not removing scrolloverflow in certain occasions
    • Fixed bug: Padding Issue with ScrollOverflow #3335
    • Fixed bug: Edge is showing an error on destroy(all) #3417
    • Fixed bug: IScroll is not defined when using Require.js to import it #2250 #2281
    • Fixed bug: setAllowScrolling not working with scrollBar:true #3392. Thanks to @dotEthan
    • Improved: accessibility issues with navigation bullets #2704
    • Improved: autoScrolling:false & scrollOverflow: true should report a warning #3403 #3406. Thanks to @dotEthan
    • Documentation: updated intro image
    • Documentation: added Vue and React links on the introduction
    • Documentation: fixed link to example #3348
    • Documentation: added links to the official React.js wrapper
    • Documentation: adding codepen link next to "Demo online"
    • Documentation: updating jsfiddle link
    • Documentation: clarifying use of licenseKey option.
    • Documentation: chinese/README.md: Fix markdown link. Thanks to @outloudvi #3419
    • Examples: fixed trigger-animations example
    • Examples: adding module loader examples: requirejs, web pack & browserify
    Source code(tar.gz)
    Source code(zip)
  • 3.0.2(Jul 26, 2018)

    • Fixed bug: parallax bounce when using offset 100% and autoScrolling:false
    • Fixed bug: input tabulation not working #3296
    • Fixed bug: data-anchor tag doesn't work #3299
    • Fixed bug: toolTip Position not correct #3306
    • Fixed bug: error occurs when clicking on nav dots #3309
    • Fixed bug: navigation dots not working when not using anchors #3320
    • Fixed bug: sectionSelector failing when using multiple separated by comma #3326
    • Fixed bug: lazy load failing in source element inside a picture element
    • Improved: fullpage can be now initialised passing the DOM object and not just a selector
    • Improved: bundled fullpage.js compatibility thanks to @steriley
    • Improved: removed traces of version 2 on the warnings
    • Examples: fixed slides background issues on backgrounds-fixed.html
    • Examples: improving some examples
    • Documentation: improved chinese docs thanks to @HiMrHu
    Source code(tar.gz)
    Source code(zip)
  • 3.0.1(Jun 26, 2018)

  • 2.9.7(Apr 9, 2018)

    • Fixed bug: Drag and Move ignores fitToSection when dragging the scroll bar on Windows #2874
    • Fixed bug: Win 7 mouse scroll issues in IE with Drag And Move on scroll bar #3143
    • Fixed bug: getPaddings is not defined" in scrolloverflow.js after resize thanks to @Odrin #3095
    • Fixed bug: console error when using empty anchor # in the URL
    • Fixed bug: incorrect behaviour of tab key when using elements with tabindex=“-1”
    • Fixed bug: Updating gulp-uglify to latest version to solve compatibility issues with minified versions of fullpage.js and webpack bundling. Thanks to @josephahern #3114
    • Fixed bug: scrollOverflow didn’t work on desktop when creating the scroll bar on resizing down
    • Fixed bug: Remove keydown handler on destroy thanks to @archferns #3124
    • Fixed bug: Remove keyup handler on destroy thanks to @archferns #3125
    • Fixed bug: CSP - Inline style violates the style-src Content Security Policy directive. Thanks to @flea89 #3170
    • Fixed bug: destroy('all') was not working when using scrollOverflow:true #3117
    • Fixed bug: wrong direction value of onleave callback when using continuousVertical #3118
    • Fixed bug: resetSliders was not working as expected when using a custom initial slide #3185
    • Improved: added the cancel scroll before it takes place in pure JS version thanks to @joelangford #3085
    • Improved: fullpage.js reported a wrong version. Thanks to @thisisfed #3161
    • Documentation: improved Chinese docs thanks to @ChangJoo-Park #3102
    • Documentation: fixing English documentation link in Korean language
    • Documentation: changed the languages menu to each language's local language
    • Documentation: added Sponsors section and included StackPath as a new sponsor
    • Tests: added a bunch of new unit tests
    Source code(tar.gz)
    Source code(zip)
  • 2.9.6(Jan 29, 2018)

    • Fixed bug: scrolOverflow didn’t work when using jQuery.noConflit() #2962
    • Fixed bug: data-srcset in picture source tags doesn't work #2865
    • Fixed bug: normalScrollElements on mobile didn’t work in fullPage.js Extensions File #3015
    • Fixed bug: afterRender was getting fired on resize #3032
    • Fixed bug: scrollOverflow + paddingTop was creating unnecessary scrollable elements on resize #3002 #2973 #2703
    • Fixed bug: using the “tab” key was breaking fullpage.js #1237
    • Fixed bug: destroy(‘all’) was not adding back original styles used before using fullPage.js #3059
    • Fixed bug: setAllowScrolling + normalScrollElements + scrollBar was failing #3050
    • Fixed bug: swipe horizontally in Firefox mobile not working when using autoScrolling:false #2741
    • Fixed bug: back history to 1st horizontal slide was broken #2706
    • Fixed bug: Reset Sliders extension did not work with Parallax #2993
    • Fixed bug: dynamically disable dragAndMove extension was not possible #2966
    • Fixed bug: parallax +scrollOverflow had issues when using background images #2827
    • Fixed bug: Fading Effect didn't get destroyed when destroying $.fn.fullpage.destroy('all') #3028
    • Fixed bug: combining parallax and fadingEffect on slides was not possible #2807
    • Fixed bug: Fading Effect unexpected animations when doing: turn off > scrolling > resizing down > turn on
    • Documentation: added official vue-fullpage.js component as a resource
    • Documentation: added Korean & Chinese docs
    • Documentation: added "how to use extensions" & "parallax" docs in Spanish
    • Documentation: improved english docs thanks to @sampaio96 and @vityavv
    • Documentation: improved Spanish docs thanks to @karnt & @alebarbaja
    Source code(tar.gz)
    Source code(zip)
  • 2.9.5(Oct 25, 2017)

    • Fixed bug: fading Effect extension issues on resize
    • Fixed bug: normalScrollElements was not working properly when using scrollBar:true #2691
    • Fixed bug: offsetSections vertical alignment issue when using scrollOverflow #2878
    • Fixed bug: offsetSections not working when using paddingTop #2876
    • Fixed bug: continuousVertical not selecting the correct navigation bullet #2917
    • Fixed bug: scrollOverflow files are not updated in bower #2868
    • Fixed bug: horizontal navigation with many elements was not centered in small viewports #2736
    • Fixed bug: setAllowScrolling was not working when using the Drag And Move feature #2705
    • Fixed bug: onLeave returning false wouldn't work on 1st or last section when using continuousVertical
    • Fixed bug: parallax animation breaks if onLeave returns false #2906
    • Fixed bug: removed JS errors when using dragAndMove:true and scrollBar:true #2892
    • Fixed bug: data-srcset in picture source tags doesn't work #2865
    • Fixed bug: onSlideLeave returning wrong direction when using continuousHorizontal #2662
    • Fixed bug: lazyLoad for audio elements didn't work #2942
    • Fixed bug: setAllowScrolling(boolean); and setKeyboardAllowing(boolean) was not undoing the setAllowScrolling(boolean, directions) and setKeyboardAllowing(boolean,directions) -Fixed bug: parallax / scrollOverflow interference: background-images lost on device orientation-change #2845 #2646
    • Fixed bug: Drag And Move extension and autoScrolling:false on mobile #2799
    • Improved: normalScrollElements for touch devices thanks to @toulatip8 #2691 #2664
    • Improved: scrollHandler was moved to scrolloverflow.js file #2250
    • Improved: remove style superContainer from CSS #2812
    • Improved: menu links don't work on anchors that begin with a slash #2803
    • Improved: applying fitToSection only in sections without fp-auto-height #1724
    • Improved: now dragAndMove extension provides more options
    • Improved: adding scrollOverflow:false when in responsive mode #958
    • Improved: adding lazyload for video elements without <source> elements
    • Documentation: added jsDelivr hits badge thanks to @LukasDrgon #2956
    • Documentation: fixed Spanish typos thanks to @BelakorrGithub #2880
    • Documentation: added extra docs in Russian and moved Spanish ones to the lang folder
    • Documentation: added eBay, BBC and Vogue in the list of sites using fullpage.js
    • Added: scrollOverflow minification build task
    Source code(tar.gz)
    Source code(zip)
  • 2.9.4(Mar 10, 2017)

    • Fixed bug: afterLoad always fires first index=1 even accessing the page on any other section #2519
    • Fixed bug: resizing viewport pauses media elements on slides #2471 #2526
    • Fixed bug: direct URL links wouldn't work when using an active slide for page load #1646
    • Added: new method fitToSection() #2575
    • Added: lazy load for elements using srcset #2355
    Source code(tar.gz)
    Source code(zip)
  • 2.9.3(Mar 1, 2017)

    • Added new option: parallax and parallaxOptions
    • Fixed bug: dragAndMove:true & setAllowScrolling not working #2506
    • Fixed bug: Chrome devices dev tools show error when using scrollBar:true #2507 #2567
    • Fixed bug: extensions file throwing error using keyboard navigation when using loopHorizontal:false #2548
    • Fixed bug: extension Drag and Move not working with resetSliders: true #2549
    • Fixed bug: dragAndMove:true & fp-auto-height cause scrolling to the top of the viewport #2551
    Source code(tar.gz)
    Source code(zip)
Owner
Álvaro
Web developer with love for beautiful stuff. https://twitter.com/imac2
Álvaro
A simple and easy jQuery plugin for CSS animated page transitions.

Animsition A simple and easy jQuery plugin for CSS animated page transitions. Demo & Installation http://git.blivesta.com/animsition/ Development Inst

Yasuyuki Enomoto 3.8k Dec 17, 2022
Simple parallax scrolling effect inspired by Spotify.com implemented as a jQuery plugin

Parallax.js Simple parallax scrolling implemented as a jQuery plugin. http://pixelcog.com/parallax.js/ Please also check our v2.0.0-alpha! We'd be hap

PixelCog Inc. 3.5k Dec 21, 2022
Lightweight, simple to use jQuery plugin to animate SVG paths

jQuery DrawSVG This plugin uses the jQuery built-in animation engine to transition the stroke on every <path> inside the selected <svg> element, using

Leonardo Santos 762 Dec 20, 2022
Matteo Bruni 4.7k Jan 4, 2023
Animator Core is the runtime and rendering engine for Haiku Animator and the components you create with Animator

Animator Core is the runtime and rendering engine for Haiku Animator and the components you create with Animator. This engine is a dependency for any Haiku Animator components that are run on the web.

Haiku 757 Nov 27, 2022
Javascript library to create physics-based animations

Dynamics.js Dynamics.js is a JavaScript library to create physics-based animations To see some demos, check out dynamicsjs.com. Usage Download: GitHub

Michael Villar 7.5k Jan 6, 2023
Create beautiful CSS3 powered animations in no time.

Bounce.js Bounce.js is a tool and JS library for generating beautiful CSS3 powered keyframe animations. The tool on bouncejs.com allows you to generat

Tictail 6.2k Dec 30, 2022
Create scroll-based animation without JavaScript

Trigger JS Create scroll-based animation without JavaScript. Sometimes we want to update the CSS style of an HTML element based on the scroll position

Trigger JS 1.1k Jan 4, 2023
A jQuery plugin that assists scrolling and snaps to sections.

jQuery Scrollify A jQuery plugin that assists scrolling and snaps to sections. Touch optimised. Demo http://projects.lukehaas.me/scrollify. More examp

Luke Haas 1.8k Dec 29, 2022
A jquery plugin for CSS3 text animations.

Textillate.js v0.4.1 See a live demo here. Textillate.js combines some awesome libraries to provide an easy-to-use plugin for applying CSS3 animations

Jordan Schroter 3.6k Jan 2, 2023
A jQuery plugin that recreates the Material Design pre-loader (as seen on inbox).

Material Design Preloader!s A jQuery plugin that recreates the Material Design preloader (as seen on inbox). I was fascinated when I first saw the pre

Aaron Lumsden 376 Dec 29, 2022
simple JavaScript library to animate texts

Animated Texts Hi, this library is a simple javascript text animator Properties force type: number default: 300 start_delay_time type: number default:

Cristóvão 4 Jan 11, 2022
Making Animation Simple

Just Animate 2 Making Animation Simple Main Features Animate a group of things as easily as a single thing Staggering and delays Chainable sequencing

Just Animate 255 Dec 5, 2022
Responsive, interactive and more accessible HTML5 canvas elements. Scrawl-canvas is a JavaScript library designed to make using the HTML5 canvas element a bit easier, and a bit more fun!

Scrawl-canvas Library Version: 8.5.2 - 11 Mar 2021 Scrawl-canvas website: scrawl-v8.rikweb.org.uk. Do you want to contribute? I've been developing thi

Rik Roots 227 Dec 31, 2022
It's a presentation framework based on the power of CSS3 transforms and transitions in modern browsers and inspired by the idea behind prezi.com.

impress.js It's a presentation framework based on the power of CSS3 transforms and transitions in modern browsers and inspired by the idea behind prez

impress.js 37k Jan 2, 2023
Super-smooth CSS3 transformations and transitions for jQuery

jQuery Transit Super-smooth CSS3 transformations and transitions for jQuery jQuery Transit is a plugin for to help you do CSS transformations and tran

Rico Sta. Cruz 7.4k Dec 23, 2022
Javascript and SVG odometer effect library with motion blur

SVG library for transitioning numbers with motion blur JavaScript odometer or slot machine effect library for smoothly transitioning numbers with moti

Mike Skowronek 793 Dec 27, 2022
🐿 Super easy and lightweight(<3kb) JavaScript animation library

Overview AniX - A super easy and lightweight javascript animation library. AniX is a lightweight and easy-to-use animation library with excellent perf

anonymous namespace 256 Sep 19, 2022
:dizzy: TransitionEnd is an agnostic and cross-browser library to work with transitionend event.

TransitionEnd TransitionEnd is an agnostic and cross-browser library to work with event transitionend. Browser Support 1.0+ ✔ 4.0+ ✔ 10+ ✔ 10.5 ✔ 3.2+

Evandro Leopoldino Gonçalves 95 Dec 21, 2022