Attending: gibson0421, m_gol, timmywil

link Sizzle issues:

• https://github.com/jquery/sizzle/issues/290 - new buggyQSA test

link Issues and PRs

• 3.0 milestone: What can be landed now?
  • Assign 3.0 milestone when accepting for 3.0
• Promises/A+ compat
  • https://github.com/jquery/jquery/pull/1821
• gibson042 proposing a change for chained .done()
• m_gol to look into better integration with tests
• Landing https://github.com/jquery/jquery/pull/1837

link Shadow DOM support

• .offset() https://github.com/jquery/jquery/issues/1784
• Sizzle roots https://github.com/jquery/sizzle/issues/296
• Wait for guidance from standards and impls

Attending: DaveMethvin, markelog, timmywil

link Additional issue tracker things

• wontfix? (done)
• cantfix?
• needs review (team needs to review the issue/PR) (done)
• I don't think we want "fixed" or "notabug", too noisy and not particularly useful to search
• "valid and fixed" issues should be assigned to a milestone, be sure they are when committing code that closes an issue
• Always set a milestone when assigning an issue, and always assign the issue before closing with a fix/patch
• Always create an issue for a PR, so the issues have a complete list of the problems solved

link Branch naming still needs to be done

• rename "1.x-master" to "compat"
• also change name in package.json - “jquery-compat”
• handle 4 remaining PRs to 1.x-master, then remove the branch; PRs:
  • https://github.com/jquery/jquery/pull/1506
  • https://github.com/jquery/jquery/pull/1652
  • https://github.com/jquery/jquery/pull/1664
  • https://github.com/jquery/jquery/pull/1704
• don’t merge anything to 1.x-master from now on
• Both versions need package.json rename to 3.0.0-pre

link Issues and PRs in the 3.0 milestone

• What can be landed now?
• Promises/A+ compat
  • https://github.com/jquery/jquery/pull/1821
• gibson042 proposing a change for chained .done()
• m_gol to look into better integration with tests

link $.xhr -- replaced by $.fetch

• Let's do this as a plugin with its own schedule

link Issues and Pull Requests

• Assign milestones to all issues

Attending: timmywil, DaveMethvin, gibson042, m_gol

link Trac issues migrated

• Do we need to consult Trac anymore? Only for historical reference
• Some recently closed tickets need to be pulled into the changelog on the next release, the list is here: https://github.com/jquery/jquery/issues/1727

link Branch naming

• "compat-only" and "master-only" for issues applying to just one -- done
• rename "1.x-master" to "compat"
• also change name in package.json - “jquery-compat”
• Both versions need package.json rename to 3.0.0-pre
• land PRs before renaming

link Promises/A+ compat

• https://github.com/jquery/jquery/pull/1653
• gibson042 proposing a change for chained .done()

link $.xhr -- replaced by $.fetch

• Should this start as a plugin? Yes

link Publish 3.0 blogpost

• Dave to do this week

link Browser support for 3.0.0

• Drop official support for Opera 12 and Safari 5.1
• Keep IE9 in the master branch
• Support Android 2.x on both (dammit)

link Additional things to reconsider as of 3.0?

• remove deprecated stuff like andSelf
• fractional width/height?

link Testing

• Continue to test Opera (latest, latest-1), but on the weekly job
• We could test Yandex browser there if it's on browserstack
• Let's switch to private browser sets (m_gol)
  • jquery and jquery-periodic
  • jquery-compat and jquery-compat-periodic

link Issues and Pull Requests

• Assign milestones to all issues
• https://github.com/jquery/jquery/issues/1784
• Shadow DOM is a pain
  • Is this something jQuery should try to fix?
  • code size and performance implications could be big
  • dave to get some input from Polymer or web standards groups on whether this is reasonable to do, and if so what devs (and jQuery) should be doing to make this work without horrible perf

link Roadmap wiki page?

• Collect all features/enhancements for feedback

Attending: DaveMethvin, jaubourg, markelog, gibson042, m_gol

link Trac

• Should migrate closed tickets (with milestone 1.12 or 2.2. or 1.12/2.2) forward to simplify the changelog - there are 16 of them
  • http://bugs.jquery.com/query?status=closed&milestone=1.12&milestone=2.2&milestone=1.12%2F2.2&group=component&col=id&col=summary&col=status&col=owner&col=type&col=priority&col=component&report=3&order=priority
• open tickets should be migrated as well :)
• dmethvin will migrate when trac feels good enough
• Re-set 1.12.0/2/22.0 milestone to 3.0.0?
• Trac still being worked on for archival use, slow progress

link Branch naming

• Have a "compat-only" and "master-only" for issues applying to just one
• rename "1.x-master" to "compat"
• land PRs before renaming

link Promises/A+ compat

• https://github.com/jquery/jquery/pull/1653
• gibson042 proposing a change for chained .done(), to be done this week
• m_gol to look into better integration with tests

link $.xhr

• markelog examples: https://gist.github.com/markelog/42d43a489afb7201ddd6
• markelog to create an implementation, working on it this week?

link version 3.0

• dmethvin making blog post, to be done this week for review

link Testing

• Continue to test Opera, but on the weekly job
• We could test Yandex browser there if it's on browserstack
• Let's switch to private browser sets (m_gol)
  • jquery and jquery-weekly
  • jquery-compat and jquery-compat-weekly

Attending: DaveMethvin, markelog, m_gol

link Trac

• Switched to GH Issues
• m_gol to find/change incorrect references to Trac
• Still need migration to Trac 1.0 for security/perf reasons
• dmethvin to monitor progress
• New registrations turned off
• Most accounts have been removed (most were spam)
• Only team/trusted logins left
• If you can log in, you can still create or edit tickets
• should migrate closed tickets (with milestone 1.12 or 2.2. or 1.12/2.2) forward to simplify the changelog - there are 16 of them
  • http://bugs.jquery.com/query?status=closed&milestone=1.12&milestone=2.2&milestone=1.12%2F2.2&group=component&col=id&col=summary&col=status&col=owner&col=type&col=priority&col=component&report=3&order=priority
• open tickets should be migrated as well :)

link Promise Error telemetry

• mikesherov will talk to Domenic

link Promises/A+ compat

• https://github.com/jquery/jquery/pull/1653
• the PR is outdated, look at the standard-then-tests-fixed branch:
  • https://github.com/jquery/jquery/tree/standard-then-tests-fixed
• needs review, now converted to std Promise rather than Q
• https://github.com/jquery/jquery/commit/d0e5c0447775239edc7819960b7c61b4b71d402f#commitcomment-7914547
• gibson042 proposing a change for .then().done() not failing, to be done this week
• m_gol to look into better integration with tests

link $.xhr

• markelog examples: https://gist.github.com/markelog/42d43a489afb7201ddd6
• strange uses of ajax setup:
  • https://github.com/search?q=ajaxsetup&ref=reposearch&type=Code&utf8=%E2%9C%93
• markelog to create an implementation

link versioning proposals (see last week for deeper discussion)

• version- and API-synchronized

• jquery 1.11.1 → jquery-compat 3.0.0
• jquery 2.1.1 → jquery 3.0.0

• methods & properties existing in both packages have identical signatures & structure for a given version
• public API MUST NOT exist only in jquery-compat distribution
• public API MAY exist only in jquery distribution
• files on cdn are jquery-3.0.0.js and jquery-compat-3.0.0.js etc.
• RESOLVED: we use the same version number for both branches
• dmethvin to make a blog post

Attending: DaveMethvin, timmywil, jaubourg, gibson042

link Update on web site attacks

link Trac

• Let's switch to Github issues
• Infra team swamped with DDoS and hack attacks
• Keeping Trac for old issues reference
  • turn off new account creation and anonymous add/comment (dave)
• Trac 1.0 upgrade will happen when it happens
• Migrate open issues to GH issues?
  • no, just close them via the current GH hook
• Create new issues with GH issues
  • turn on gh issues (dave)
  • create tags/milestones

link Promise Error telemetry

• mikesherov will talk to Domenic

link Promises/A+ compat

• https://github.com/jquery/jquery/pull/1653

• needs review

• should this deliver to the .then? It doesn't currently because the .done throws
  • Deferred().done(f1).then(f2)
• gibson042 proposing a change for that

link $.xhr

• markelog examples: https://gist.github.com/markelog/42d43a489afb7201ddd6
• Can this be made to work with jquery-compat? (1.x)
• IE8 limitations
  • http://blogs.msdn.com/b/ieinternals/archive/2009/07/23/the-ie8-native-xmlhttprequest-object.aspx

Attending: DaveMethvin, markelog, jaubourg, gibson042, mikesherov

link Trac

• just about at the end of the line if it doesn't get fixed soon
• we will switch to gh issues next week if trac has no progress

link Promise Error telemetry

• Domenic proposed unhandled rejected promises go thru window.onerror
• he actually preferred a separate handler for it tho
• which should we back?
• mikesherov will talk to Domenic this week

link Promises/A+ compat

• jaubourg is working on it

link $.xhr

• markelog and gibson042 to create some examples based on typical ajax usage
• emails going out to core mailing group, with gists of sample usage
• jQuery.ajax docs have some good examples

link https://github.com/jquery/jquery/pull/1652#issuecomment-56127735

• bring back clear/mergeAttributes, gibson042 is on it
• doing some perf tests to see impact

Attending: DaveMethvin, gibson042, mikesherov

Note: Timmy on vacation Aug 31-Sept 21

link Trac

• I will ping about that, i think they made progress last week

link Promises/A+ compat for jaubourg's pull request

• m_gol got it mostly working
• some fails related to invalid args
• need a solution for dfd.done( fnThrows ).then( neverCalled )
  • keep a separate list of callbacks for .then() vs .done()?
• need analog to Promise.unhandledRejection proposal from Domenic
  • http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2014-September/297601.html
  • (questions about whether onerror or unhandledRejections is best)
• see if jauborg and m_gol can finish this
• Promises error telemetry - Mike to reach out to Domenic

link $.xhr

• markelog and gibson042 to create some examples based on typical ajax usage
• review at next meeting

Location: In person, Chicago jQCon

Attending: DaveMethvin, markelog, gibson042, m_gol

link Versioning

• If we are going npm we should obey semantic versioning
• The .then() change will be breaking
• Might as well remove other things like .andSelf()
• New versioning
  • 1.x now jquery-legacy-3.x
  • 2.x now jquery 3.x

link Deferred pull request for Promise/A compat on .then()

• Comments on the PR
• A branch with tests applied:
  • https://github.com/jquery/jquery/tree/standard-then-tests (run grunt promises-aplus-tests)

link xhr

• Design goal: allow standalone usage
• Simple xhr module in a wrapper

jQuery.xhr = require("jquery-xhr");
jQuery.xhr.Promise = window.Promise || function( executor ) {
    var dfd = jQuery.Deferred();
    try {
        executor( dfd.resolve, dfd.reject );
    } catch ( ex ) {
        dfd.reject( ex );
    }
    return dfd.promise();
};

• Simple case: jQuery.xhr( url, options ).then( handlerA ).then( handlerB )
• beforeSend case:

xhr = jQuery.xhr( url, { autosend: false } ).set( … );
jQuery.xhr({ url: ... });
jQuery.xhr( url );
xhr.then( handlerA );
xhr.send( body ).then( handlerB )

• Super-advanced case:

xhr = jQuery.xhr( url, { autosend: false } );
xhr.then( handlerA );
if ( badFeeling(xhr.getNative()) ) { xhr.abort(); }
xhr.send( body ).then( handlerB );
Promise.resolve( xhr ).then( … )
jQuery.xhr( url ).send({ ... }), jQuery.xhr( url )

• Does an unsent Promise that has mutability violate the Promise/A+ spec? Or does the mutability only apply to the resolution? No. Does not appear to apply to the returned promise, which can be augmented, only to the resolved value of the promise
  • https://people.mozilla.org/~jorendorff/es6-draft.html#sec-promisenew
  • https://github.com/promises-aplus/promises-spec
• options necessary to functionality: method, user, pass, body, query (RFC), beforeSend
• options nice to keep: cache, ifModified, headers
• jxrPromise: .abort(), .xhr property
  • Rejects on: Exception, timeout, abort
• what about 4xx/5xx? or a 0 (network error)
  • implied success: jQuery.xhr( url ).then( jQuery.xhr.rejectHTTPError )
  • implied failure: jQuery.xhr( url ).catch( jQuery.xhr.ifResponse )
• Resolved value: raw native xhr
• Rejected value: Error object, potentially with .xhr property, .options object

Attending: DaveMethvin, markelog, gibson042,

Note: Timmy on vacation Aug 31-Sept 21

link Trac

• Volunteers are making progress on new setup
• Had two new volunteers, including a Trac core contributor

link Promise/A+ compat

• gibson042 proposal seems like it should work!
• Checking with jaubourg on his availability, markelog and gibson042 are interested

link $.xhr

• Build options object interface
• Below it is a chaining interface?
  • exposes (not wraps) underlying xhr method
• limited compat with old IE and ActiveX method?
  • (See discussion in IRC)

link Pull Requests

• Please review and comment
• markelog to land a few today
• gibson042 and dmethvin to work on them tomorrow

link Tickets

• 1.12/2.2 tickets: http://goo.gl/NsAfgV
• http://bugs.jquery.com/ticket/15205
• tickets needing an owner: http://goo.gl/v8YQdp