-
Notifications
You must be signed in to change notification settings - Fork 19
/
changelog.txt
103 lines (61 loc) · 3.54 KB
/
changelog.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
PolyPage Change Log
0.9.1
- Fix default states.
0.9
- Some performance improvements.
- Provide hooks for custom show/hide animations via base:{ show:func, hide:func }
- options for ppBase now go on the root object... {base:{opts}} becomes {opts}
0.8.3
- Split extensions out into separate files to make mix'n'match easier.
- Extensions are now auto loaded into the $(el).polypage() function when they are available.
0.8.2
- Fixed a regression which broke alphabetical sorting.
- Added a new extension to handle keyboard shortcuts. (ALT + first_char_in_state_name toggles the state)
- Added a friendly error message when you have syntax errors in class names.
0.8.1
- Readme updates.
- extensions now take a 'polypage' option to assist with custom bindings.
- API Change, ppbase options are now passed in via $(el).polypage({ base: {} }); so it is inline with other extensions.
0.8
- This release is a big refactoring to split the PolyPage logic into a Base library and series of smaller modules.
- A public event API for triggering page state changes and being notified of them.
- The plugin now is a real JS object so theoretically you could have several PolyPage's co-existing on one html page.
- PolyPage now follows the jQuery standard and is fully chainable, and scoped, in most cases $(document).polypage() is fine.
- The GUI, Event bindings and Cookie support is now 100% independent of the polypage Base functionality. You can now run polypage with no GUI or DOM injection at all.
- A decent amount of high level test coverage on the key components.
0.7
* Officially note the MooTools branch.
* Added a test suite around the public API, this was long overdue, sorry.
* Pulled in some of Yoan's changes to allow #state tiggering on 'a' and 'form' elements.
* Started a skins folder based on Rich's suggestion, if you've got any good ones I would love to have them in the repo.
0.6
* PolyPage can now be intialized on a jQuery collection using the $(selector).polypage() syntax. the matched elements are used as the container for the navigation controls. This is now the recommended way to initialize jQuery although the $.polypage.init() method still works for backwards compatibility at the moment. (Thanks to Phil Oye)
* Some refactoring of cookie support and setState();
* Fixes a bug where setting a cookie and a hash in the url to both be on would cause an infinite loop of toggling.
* Added a customizable label to make it clear the toggles are page states, use the 'label' option to change. (Thanks to Phil Oye)
* Increased the specificity of the CSS selectors so they are unlikely to be affected by other page styling.
* If no PolyPage elements exist on a page then we now avoid adding an empty toggle box to the page. (thanks to Phil Oye for the suggestion)
* The 'pp' classname prefix can now be changed via the 'prefix' option.
* The classname separator can now be changed via the 'separator' option.
0.5.1
* Upgraded to work with jQuery 1.3.x
* Fixed a CSS typo
0.5
* Regex improvements
* Support for numbers in state names.
* Safari 3 support.
* Alphabetically sort states in the toggle list to avoid confusing users with changing orders across different pages.
* IE6 support.
* Anchor the toggles to the top of the html rather than the viewport.
0.4
* Fixed a major bug with cookies, all cookies are now scoped to the root of the domain. (thanks Nat)
0.3
* Added cookie support.
* Wrapped the plugin in a closure.
* Added MIT & GPL Licenses.
0.2
* Upgraded jQuery.
* Fixed some false negative results.
* Made the syntax slightly easier.
0.1
* Initial release.