-
Notifications
You must be signed in to change notification settings - Fork 2.4k
Write unit tests for single module support #5987
Comments
@jzaefferer for listview specifically this can now be used independantly with out pages on the js side on master, @uGoMobi is working on fixing up the css to match on branch next so the classes you mention will not be needed. toolbars & navbars also work independent of pages in branch pageSections. Hoping to be able to do the same with the rest of the widgets for 1.4 |
Ticket for listviews without page: #5429 (this is fixed in branch "next"). |
This is labelled "Fixed in next", since that branch landed in master, does that means this ticket can be closed? |
I added that label when the work on listview was done in branch "next", but didn't close the issue after the merge because I realized the ticket is not only about listview. This is not done yet for all widgets or the changes are still in branches, so I'll remove that label. |
Are there still widgets that don't work outside page / without init module? |
Yes. Collapsibleset does not work without the page, because the page contains the code that causes initSelector to be added to the collapsible constructor ( |
Controlgroup will also not work because it too relies on initSelector. |
Both modules have a hard dependency on the "vmouse" module that should be expressed in AMD. Re jquery-archivegh-5987 Closes jquery-archivegh-7274
Both modules have a hard dependency on the "vmouse" module that should be expressed in AMD. Re jquery-archivegh-5987 Closes jquery-archivegh-7383 Closes jquery-archivegh-7274
@arschmitz Can this be closed as we have individual modules now? |
Yes but lets open issues for any widgets which dont have an individual module test already i think there are still a acouple |
As discussed on the jquery-devs-team mailing list. These were my notes about issues when trying to use jQuery Mobile without the init module, in a very simple example:
Apart from an issue with nested listviews its mostly adding classes to various elements: ui-mobile to
<html>
, ui-mobile-viewport to<body>
, ui-page and ui-page-active to a<div>
that contains the actual content. And a few swatch classes to make things look okay.Doesn't seem so bad now, but since this approach isn't documented anywhere (right?), I had to cobble that together from the generated markup. And the example really wasn't doing much. just a header, footer, a bit of navigation and a listview.
The text was updated successfully, but these errors were encountered: