- 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)
Author Archives: builder
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?
jQuery Core Team Meeting – Dec 15 2014
Attending: DaveMethvin, m_gol, gibson042, markelog, timmywil
link 1.11.2/2.1.2 release
- All patches landed? They should all be here:
- Trac tickets listed under a single GH issue
- https://github.com/jquery/jquery/pull/1662 was master only
- Sizzle has been updated in master, compat, 2.1-stable, and 1.11-stable
- Add Ajax URL sanitization?
- https://github.com/jquery/jquery/issues/1875
- No, let's leave until 3.0, there are compat risks
- Release ASAP
- Need blog post draft
- Has jquery-release been updated to not copy -latest? I think so
- (in general, any changes to jquery-release needed?)
link 3.0 release - target mid-January
- Major blockers or unassigned tickets?
- Should we switch to ES6 module format for authoring?
- Can still generate both the monolithic file and AMD from that
- Move AMD modules to dist/AMD
- Breaks the build process, can’t use r.js or var modules
- Can’t load modules when testing
- Decided to not change authoring for 3.0 … wait for 4.0, better tooling and/or browser support before using ES6 for authoring
- QUnit ticket: https://github.com/jquery/qunit/issues/707
link Issues vs Pull Requests
- Let's use issues (only) for changelog
- PRs should have one or more issues, unless they're housekeeping (e.g. typos and such) in which case we don't need an issue
- Need a commit message format change here?
- gibson042 has Component name enforcement
- Support for jquery-release to build changelog
link Issues and PRs
- Promises/A+ compat
- https://github.com/jquery/jquery/pull/1821
- gibson042 to work on a PR
- maximum backcompat, allow setting context, multiple resolved values, etc. (Promise/A compat for code that draws inside the standard lines)
- Use a plugin to handle the error cases?
- Might be able to use try/finally now that IE7 has been dropped
- Plain Objects
- https://github.com/jquery/jquery/issues/1776
- Do we support animation on Object
- https://github.com/jquery/api.jquery.com/issues/600
- Are the docs/units correct and complete compared to code?
- https://github.com/jquery/jquery/pull/1668
- Should we hide the expando on plain objects? Let's try exposing it and see if anyone depends on it
- Should we add .animate() and .queue() to the list of things supported for plain objects?
- .queue - yes, support on plain objects, little impact
- .animate() - let's look at velocity.js, although it may be as simple as guarding stuff with .nodeType checks