Category: jQuery Core Team

Minutes from jQuery Core Team meetings

jQuery Core Team Meeting – Aug 12 2013

Attending: jaubourg, m_gol, orkel, timmywil

link Jenkins/testswarm status

  • problems with ajax requests (server side problems - gnarf working on it)
  • line-height unit-tests are unstable
  • Sizzle.attr failures in IE6-7

link jQuery 1.11/2.1

jQuery Core Team Meeting – Aug 05 2013

Attending: DaveMethvin, orkel, gibson042, timmywil

link Jenkins/testswarm status

  • Browserstack fixed their IE9 issue (thanks Krinkle)
  • boxSizingReliable patch to make FF stop complaining (orkel has a pull)
  • "order" (orkel to remove the unit test since it's browser-specific)
  • oldIE tests fail but only on swarm (check with testing team)
  • Let's get to where we can trust the unit tests in Jenkins/swarm

link jQuery Migrate

  • Fail on Migrate attribute test (Krinkle created issue in Migrate tracker)
  • A few other small issues
  • Consider a new release soon, gibson042 to look next week

link jQuery 1.11/2.1

  • AMD status (timmywil)
  • Performance tests (orkel)
  • Can we have a dashboard that combines units, perf, coverage?
  • What's the first step? orkel is working on that

link Pull requests

link Bug triage

jQuery Core Team Meeting – Jul 29 2013

Attending: DaveMethvin, timmywil, orkel

link Jenkins/testswarm status

  • "order" failure - m_gol to do a patch
  • Still need to update browsers? (Krinkle is checking)
  • Fail on Migrate attribute test (gibson042 to check)

link jQuery 1.11/2.1

link Bug triage

jQuery Core Team Meeting – Jul 22 2013

Attending: DaveMethvin, orkel, timmywil, m_gol

link Jenkins/testswarm status

  • http://swarm.jquery.org/job/901
    • "order" failure - m_gol to do a patch
  • How to make the ajax tests reliable?
    • dmethvin to check with test team
    • orkel says it may have been a temporary prob with jenkins
    • Need to update browsers in testswarm, orkel to check with Krinkle

link jQuery 1.11/2.1

link Bug triage

jQuery Core Team Meeting – Jul 15 2013

Attending: DaveMethvin, orkel, timmywil, m_gol

link Switchover to Bower (timmywil)

  • Change is made for master and 1.x-master
  • Working for everyone?
  • Issues?
    • Our build process with bower is fine, Sizzle and QUnit
    • Can't publish jQuery to Bower yet tho
    • Need to wait until they are released
    • Current Bower package forces Migrate on everyone
    • Wait for Bower update

link npm version

  • need a change to module.exports, wait for 2.0.4

link Problems with Jenkins/testswarm

  • Post to .html pages is too error prone
  • Causing AJAX fail
    • Create a PHP-based page to get test files (dave)

link jQuery 1.11/2.1

  • Dave didn't summarize the doc yet
  • make .ready() optional in its own module
    • solves the cross-dependency issue nicely!

jQuery Core Team Meeting – Jul 08 2013

Attending: DaveMethvin, orkel, timmywil, jaubourg, gibson042, rwaldron

link 1.10.2/2.0.3 release

  • Any problems? None reported

link Problems with testswarm

  • ngnix not configured properly, 502 on post to static pages
  • long term problem
  • what can we do to fix soon?

link jQuery 1.11/2.1

  • https://docs.google.com/document/d/1oQ966Lq9szqP41BehdlmAJV33lgNcrE0C0tktLvIz5s/edit
  • (action items and conclusions below summarized from meeting discussion)
  • requestAnimationFrame - Do not pull into core, gnarf has a plugin for people who want it and we'd still break a lot of existing code if it was the default
  • Alternative animation API (initially a plugin) - leave to third parties
  • Alternative AJAX implementation - jaubourg to noodle over
  • Deferreds and Callbacks optional modules - yes, after AMD is settled
  • make .ready() its own optional module - yes, and discourage its use
  • Use AMD - yes, timmywil is on it
  • Deprecate/remove jQuery.support? - Can't remove, but move feature detects into their respective modules and make them lazy, reduce forced layouts; next step to be done after initial AMD is finalized
  • Avoid offsetHeight/offsetWidth completely - yes, mikesherov?
  • Attach data directly to elements

jQuery Core Team Meeting – Jul 01 2013

Attending: DaveMethvin, timmywil, jaubourg, orkel

link Node and other non-browser setup

link Tagging Sizzle

link jQuery 1.10.2

link jQuery 2.0.3

link 1.10.2/2.0.3

link Release dates?

  • Tomorrow for both

link Followup for 1.11/2.1 issues discussed at in-person Portland

  • Dave to send email with agenda based on meeting notes
  • Discuss in meeting next Monday, or add notes if you can't make it to the meeting

jQuery Core Team Meeting – Jun 24 2013

Attending: timmywil, m_gol, rwaldron

link jQuery 1.10.2

link jQuery 2.0.3

link 1.10.2/2.0.3

  • Next Monday/Tuesday for both?
  • Monday after meeting

link jQuery 2.1/1.11 changes

  • Discussed at in-person Portland meeting
  • Private meeting notes need to be processed
  • Let's put on agenda for next week

link Style guide updates

jQuery Core Team Meeting – Jun 03 2013

Attending: timmywil (married), gibson042, DaveMethvin, m_gol, orkel, gnarf, scott_gonzalez (style discussion)

link jQuery 1.10.2

link jQuery 2.0.3

link 1.10.2/2.0.3

link Can we wait until after Portland for a new release?

  • let's try … gotta monitor the duplicate tix

link Intel wants to help with some optimization issues

  • Rich Winterton profiled with VTune, saw bad JITting behavior
  • But...are any on hot paths?
  • Maybe we can meet with him in person next week?
  • Collab with Intel App Framework

link jQuery 2.1/1.11 changes

  • Discuss at in-person Portland meeting
  • Some thoughts
    • Make Deferreds and Callbacks optional modules
    • Deferred used in .ready() only, never documented
    • Use AMD to do our module builds? snover has a branch
    • needs updates to grunt build
    • optional dependencies (Deferred in .ready) are tricky
    • Does defaultDisplay really solve a problem?
    • Only reliable way is to append, THEN hide. That doesn't cause extra reflows does it?
    • Our "visible" check causes reflows, can we fix that?
    • Need to use display:none vs .offsetHeight/Width
    • Would fix issues like
      visible bug
    • Either changes the meaning of visible, or requires climbing the tree to determine visibility
    • Avoid offsetHeight/Width completely
    • Always a whole number
    • Screws up zoomed results and subpixel rendering
    • Attach data directly to elements for faster teardown

link Style guide updates

  • Grouping parens need space? (i.e., ALL parens need space)
    • If so do all { need trailing newlines?
    • e.g. var x = { test: true } would be invalid
    • Do all ? and : need surrounding space?
    • We tend to do b ? v1 : v2;
    • But we do { test: true } no leading space on colon
  • Dave to make a pull request against the style guide for comment

link Open tickets triage

jQuery Core Team Meeting – May 27 2013

Attending: m_gol, jaubourg, dmethvin, gnarf, orkel

Official Agenda:

link jQuery 1.10.1/2.0.2

link jQuery 2.1/1.11 changes

  • Discuss at in-person Portland meeting?

link Open tickets triage