jQuery Core Team Meeting – Jun 30 2014

Attending: gibson042, markelog, m_gol, timmywil, DaveMethvin

link Sizzle on npm; ender support; browserify support

link $.xhr strawman

  • please provide feedback in the gist
  • Promise support - thenables only?

link Download builder in 1.12/2.2?

  • already a third-party one
  • might encourage more subset use and reduce bloat whining
  • need to warn people about third-party code needing everything

link Test fails

link Pulls

  • I suggest we don't land for API consistency -- done

link Tickets

jQuery Core Team Meeting – Jun 23 2014

Attending: timmywil

link Test fails

link Pulls

link Tickets

jQuery Core Team Meeting – Jun 16 2014

Attending: DaveMethvin, m_gol, gibson042, markelog

link Test fails

link Pulls

link Tickets

jQuery Core Team Meeting – Jun 09 2014

Attending: DaveMethvin, markelog, m_gol, gibson042, scott_gonzalez, timmywil

link 1.12/2.2 - Let's get going

link Pulls

  • QUnit eliminating globals
  • Increase the set of tested browsers in Sizzle

link Tickets

  • Decode by type regardless of status code?
  • Compat impacts? Nobody should be depending on errors not decoding at this point we could assume?
  • Let's leave $.ajax as is and push folks towards $.xhr
  • We aren't testing in this env (or several others like Win8)
  • Ways to do this?
  • No obvious solutions here that are easy
  • :visible, :hidden behavior change
  • empty elements (with 0 height) will be hidden instead of visible
  • Although, they were only visible in some browsers
  • Will now be consistent for empty elements and

jQuery Core Team Meeting – Jun 02 2014

Attending: DaveMethvin, timmywil, m_gol, gibson042, markelog

link 1.11.2 / 2.1.2 watch

  • Anything that requires a patch release?
  • If not, let's start landing 1.12/2.2 changes

link Pulls

  • Wrap depends on clone
  • Ajax depends on events - remove that
  • License changes for consistency
  • QUnit eliminating globals
  • Interop with standard Promise
  • Sizzle testing:

jQuery Core Team Meeting – May 19 2014

Attending: DaveMethvin, m_gol, timmywil, markelog, gibson042

link 1.11.2 / 2.1.2 watch

  • Anything that requires a patch release?

link Bugs

  • use isNaN instead?

link Pulls

  • Use page viz api to determine whether to run animation
  • too big to land as-is
  • see if we can work with him to reduce

link Failing IE6/7 tests in .data()

  • Source of the problem isn't clear, very few changes recently
  • Could be the <object> tests, maybe a change at BrowserStack
  • m_gol to check with BS

link Google bug bounty

  • Replied to them with a go-ahead based on team response

link 1.12/2.2 planning

jQuery Core Team Meeting – May 12 2014

Attending: DaveMethvin, m_gol, timmywil, markelog, gibson042

link 1.11.2 / 2.1.2 watch

  • Anything that requires a patch release?

link Angular use of .data()

  • Makes use of jQuery._data()
  • Issues:
    • copying _data(node, ‘events’) won’t work with events with setup/teardown hooks
  • Should we expose in the 2.x branch so Angular 1.3 could use it?
    • Yes, we need to leave jQuery._data() in place
    • Perhaps document so people would know to leave it alone?

link Pulls

link 1.12/2.2 planning

jQuery Core Team Meeting – May 05 2014

Attending: DaveMethvin, m_gol, gibson042, timmywil, markelog

link 1.11.1 / 2.1.1

  • Shipped last week
  • Any feedback or bugs?
  • Let's make this the last before 1.12/2.2 barring bad regressions

link The demise of jquery-latest

  • Google folks are on board to make /1/ point to 1.11.1
  • Dave to make a blog post

link 1.12/2.2 planning

link CSS selector escaping?

jQuery Core Team Meeting – Apr 28 2014

Attending: DaveMethvin, timmywil, m_gol

link 1.11.1 / 2.1.1 RC2

  • Shipped last week
  • Any feedback or bugs?

link 1.11.1 / 2.1.1 final

  • Release? How about Thursday 5/1
  • Code changes to land:

link Sizzle pulls

link Velocity: replacement for $.animate

link 1.12/2.2 planning

  • Tickets and pulls already tagged
  • Who wants what?
  • Take a look and let's discuss next week
  • We'll do async

jQuery Core Team Meeting – Apr 21 2014

Attending: DaveMethvin, timmywil, markelog, gibson042

link 1.11.1 / 2.1.1 RC

  • m_gol did RC1
  • I published an RC1 blog post for about 5 minutes
  • I missed the update required to Sizzle (but there was a ticket)
  • gibson042 landed it Friday
  • Dave set up a VM, can (or will try to) publish the beta today
  • To simplify, let's call this RC2 and not speak of RC1 :-)

link "browser" KEYWORD for npm

link Open tickets for .1 release

  • IE11 being stupid
  • Way to prevent accidental release without latest Sizzle
  • slideUp/Down on inline elements
  • We're getting a ton of spam on the tracker
  • Ideas on how to reduce it?
  • Delete the spammy posts when you see them
  • Lots of fake logins being created as well