- Ticket triage
- 394 tickets total +2
- 34 pull requests -3
- 1.11.x Regressions
- AMD
- Use AMD loader in demos and tests
- Rafael to refactor helpers into single file not loaded via AMD
- Jörn to review again after that change
- Classes option
- Alex testing new implementation with _addClass() and _removeClass()
- Jörn did another round of review
- Alex to make updates based on review
- Button
- New button PR
- Alex to push update based on classes changes
- Jörn to review after the classes update
- RTL
- All tickets
- The obvious changes are element locations swapping, but there are some more complex situations:
- #5440 Theme - icon placement, scrollbars (from hidden content?)
- #10655 Menu - arrow keys for opening submenus
- #10658 Slider - lowest value on the right
- Suggestion: Use
dirattribute in markup to determine direction instead of using an option - PR for spinner based on this suggestion
- Alex to ask Ariya for his contact. Hoping for help from IBM, at least with testing. Also ping Hans Hillen and Dylan Barrel
- Scott to schedule a call to hash out details with all those who have experience and are willing to help.
- Compare KendoUI implementation
- Jacques to bring up RTL on IBM's internal governance call
- Tooltips in native dialogs
- #10739
- Scott to ping browser vendors and spec authors about odd overflow constraints
- Selectmenu
- Should we check for hidden options?
- Alex says hiding options isn't consistently supported natively
- Alex to close with explanation
- Perhaps we shoud advise him to use disabled attr in addition to display:none and hide the generated, disabled items via CSS.
- New default theme
- Rafael testing DB/TR integration
- Decided to make the new theme the new default, as "Base", keep UI Lightness and Smoothness in the TR gallery
- Update tooltip to use ui-widget-shadow class (via classes option, once that lands), move box-shodow definition into theme.css/.ui-widget-shadow, update TR to demo that instead of the weird fake shadow we have currently
Author Archives: builder
Chassis Team Meeting – Jan 06 2015
- Determine which SVG icon set to use #1
- Initial discussion to cover which icons to support from the get go, based on current discussion in the issue
- Decided to start out by created a SVG icon builder for just 3 placeholder icons to test the ability to select certain icons for builds, add in custom icons, replace icons, etc. michaelarestad to make a PR
- Style Guide #11
- Discussions in issue were leaning towards generated documentation.
- Decided we needed to specify what we're talking about when mentioning "Style Guide," since the issue was getting slightly off topic compared to original description. (For example, Code Style Guide vs Pattern Library vs Design Style Guide). Issue is leaning towards auto-generated (or not) docs instead of "pattern library," which is really more what the topic was about. sfrisk renamed issue to "Pattern Library" to help focus issue. Discussion involving the generation of documentation moved to a separate issue/ Concerns raised regarding inline (auto-generated) documentation and how it could clutter code. Also discussed need for code style guides for scss and html.
- File structure #29
- MichaelArestad and cbracco opting for atomic structure in issue
- Majority leaning towards atomic structure, with 100% complete modularity and independence. Discussion turned to possibly bundeling component styles with components rather than in the sass folder (possibly going the include/require an external spreadsheat route). Example here. However, general opinion seemed to be that putting components styling outside of the sass folder might be harder for new people to follow. Pros for that method would be making it easier to use just a button (for example), without pulling down everything in the repo. However, with a good builder, this shouldn't be a problem (similar to what has been done in jQuery mobile)
jQuery Core Team Meeting – Jan 05 2015
Attending: DaveMethvin, gibson042, markelog, arthurvr
link jQuery 3.0 beta
- Still a LOT to do
link Pull Requests and Issues
- indexOf
- Seems good to have a consistent standard
- Would need to be addressed in the style guide?
- In the meantime, land the two PRs
- land this, we can tweak
- Can we eliminate $.support.cors and use XHR as the default transport if no other transport works?
- Would eliminate a lot of special cases
- Pinged @jaubourg on the possibility
- Skip PATCH tests on BrowserStack
- too many spurious fails from their setups for some reason
jQuery Core Team Meeting – Dec 29 2014
Attending: DaveMethvin, gibson042, arthurvr, m_gol, timmywil (12:45)
link Reminder: 3.0 in two weeks!
- Need owners for several tickets
- Need to land exising PRs
link Issues and PRs
- https://github.com/jquery/jquery/issues/1969
- Is unescaped \f valid in an XHTML document attribute value?
- Is there some way we can avoid constant XHTML issues? Can we test in XHTML perhaps for an occasional run?
- m_gol to look at https://github.com/jquery/jquery/issues/1731
- https://github.com/jquery/jquery/issues/1967
- jQuery.support.cors is in relatively wide use (but not formally documented) for situations like PhoneGap and IE local apps
- Can this be fixed by selecting XHR as a default transport?
- Continue discussion on the ticket
- https://github.com/jquery/jquery/issues/1956
- Get using .html() (avoiding encoding) and set as .text()?
- Asking on the ticket why that can't be done
Chassis Team Meeting – Dec 23 2014
- Naming convention #4
- Going with BEM, considering using double dashes. We shall open up a new issue for design patterns
- Performance Testing #2
- Need to come up with a list of frameworks, what test pages will contain, and will they be individual components or like a kitchen sink (if later, will need to find a common set of components between various frameworks). Add note regarding that to #2
- Create Logo #27
- isaacdurazo will have time to work on logo after the 5th
- Next Week's Meeting
- Due to the holidays, many people won't be around next week. Canceling meeting for next week. Chassis meeting to continue on January 6th.
jQuery Core Team Meeting – Dec 22 2014
Attending: DaveMethvin, gibson042, gnarf, m_gol, jaubourg, markelog
link 1.11.2/2.1.3 release
- Done
link Issues and PRs
- Format of // Support: comments
- https://github.com/jquery/contribute.jquery.org/issues/95
- Spaces around the numbers and symbols, consistent with JS spacing
- Documenting a ready promise
- https://github.com/jquery/api.jquery.com/pull/530
- Currently on jQuery.ready, but that's an internal method
- m_gol has https://github.com/jquery/jquery/issues/1778
- Revisit after that ticket is resolved
- Text of a script tag
- Smoke-testing on Node, not assuming the browser env in source
link Code coverage
- markelog to create an issue
jQuery Mobile Team Meeting – Dec 18 2014
- Ticket Triage:
- 262 tickets +0
- 34 pull requests +0
link 1.5.0
- Waiting on changes from ui
- Classes
- Working on upstream changes
- Button
- CSS update (button, checkboxradio, controlgroup)
- Jasper continued to work on https://github.com/jquery/jquery-mobile/pull/7753
- CSS update (button, checkboxradio, controlgroup)
- Auto Init
- New module details
- removing nojs its not documented
- New module details
- data- attribute name space
- backcompat
- Pointer Events
- transfered
- CSS Framework
- https://github.com/jquery/css-chassis/
- Chassis is the chosen name
- https://github.com/jquery/css-chassis/
- Popup on Android
- https://github.com/jquery/jquery-mobile/issues/7862
- Going to make a PR with the patch, because it seems good enough
- https://github.com/jquery/jquery-mobile/issues/7862
- Events split-up
- https://github.com/jquery/jquery-mobile/issues/7805
- Going to make a PR so we can decide where to put common code in lieu of $.mobile (because events do not depend on
js/ns.js)
- Going to make a PR so we can decide where to put common code in lieu of $.mobile (because events do not depend on
- https://github.com/jquery/jquery-mobile/issues/7805
jQuery UI Team Meeting – Dec 17 2014
- Ticket triage
- 392 tickets total -4
- 37 pull requests +2
- 1.11.x Regressions
- AMD
- Use AMD loader in demos and tests: Reviewed with Jörn. Still need to refactor to load helpers statically before requirejs, should fix some of the regressions.
- Classes option
- adding _toggleClass() with required boolean parameter
- Will handle auto-removal of classes on destroy
- Removing null nested option values
- Effects
- Landed!
- Pointer Events
Testing Team Meeting – Dec 17 2014
- QUnit
- Released 1.16.0
- Fixing regressions
- Discussing QUnit.test(name) as an alternative to QUnit.skip(name)
- Testing Infrastructure
- Still trying to get browserstack-runner working on Travis
- Also get Globalize unit tests to pass on browserstack-runner
- CSS Testing
- Alex to ping Kristofer (Topcoat)
Chassis Team Meeting – Dec 16 2014
- Naming convention #4
- Phone call with Yandex regarding BEM happened this morning
- BEM seems to be the prefered naming convention
- Performance Testing #2
- No news on this at this time
- Decided to start working on our own solution
- Domain Names
- We need to buy domain names
- kborchers to buy the domain name css-chassis.com
- Documentation
- Should we use jquery-wp-content? Don't inherit from base theme to be able to use self-hose?