Author Archives: builder

jQuery Mobile Team

jQuery Mobile Team Meeting – Mar 20 2014

jQuery UI Team

jQuery UI Team Meeting – Mar 19 2014

  • Ticket triage
    • 3 pending tickets +1
    • 403 tickets total +3
    • 39 pull requests +2
  • Button
  • Globalize
  • Release
    • Working on migration to jquery-release
    • Making a fake-project so that its much quicker to test changes in jquery-release
    • Checking for required executables
    • Improving Release.exec and simplifying grunt calls everywhere
  • browserstack-runner
    • Collaboration with BrowserStack on their runner
    • Now supports compact configuration and decent output for QUnit
    • Needs some more improvements
jQuery Core Team

jQuery Core Team Meeting – Mar 17 2014

Attending: DaveMethvin, gibson042, m_gol, markelog, timmywil

link 1.11.1 / 2.1.1

  • Create new ticket to rewrite XML tests to avoid them being cross-document
  • The PR to be nixed in favor of removing cross-doc manip in tests
  • Ticket: http://bugs.jquery.com/ticket/14796
  • Looks like we do need to fix this
  • dmethvin to land
  • Push to 2.2 because it's ugly
  • m_gol to write a test failing in IE8
  • let’s blacklist iOS7 and wait (forever) for a real bug report
  • Please land your fixes ASAP

link Old browser job

  • Still broken, it's an infra problem most likely

link Failing oldIE tests -- how to fix?

  • Wait until we switch to karma

link Browser support blog post

  • Still need UI team input
jQuery Mobile Team

jQuery Mobile Team Meeting – Mar 13 2014

jQuery Core Team

jQuery Core Team Meeting – Mar 10 2014

Attending: DaveMethvin, markelog, gibson042

link 1.11.1 / 2.1.1

  • Looks like we do need to fix this
  • Land now?
  • Just document cssNumber? YES
  • Don't want to embed non-W3C vendor-specific properties
  • LGTM
  • m_gol: I’d hold off, probably reverting the !important patch will fix it by itself. I’d just land the tests
  • Please land your fixes ASAP

link Old browser job

  • Failing oldIE tests -- how to fix?
  • Revert fake timers? I hope not.
  • Wait until we switch to karma
  • Browser support blog post
  • Still need UI team input
  • $.fn.data
  • Land this in 1.12 / 2.2? YES
  • Should we fix the clearly broken 2.1 now? NO
jQuery Mobile Team

jQuery Mobile Team Meeting – Mar 06 2014

  • Style option removal
    • Might increase CSS size, leading to longer startup time.
    • Certain widgets support certain options. If it's just classes, users might try to add any class to any widget.
    • Kangsik: There will be too many classes and too many ways of adding them - sometimes to data-wrapper-class, sometimes to class. It will be harder to use jQM.
      • keep non-bool style options like theme, icon, and iconpos; look into deprecating theme swatches for 1.6
  • Collapsible collapsed/collapsed-icon/expanded-icon
    • Might be doable entirely in css with, maybe, like .ui-icon-expanded-plus and .ui-icon-collapsed-plus, etc., but again, it would probably add a lot to the CSS, increasing startup time.
  • Shadow option
    • If we change the default to false, is there a way to provide a deprecation period?
    • We could add a shadow even if no class is specified, and then create a class ui-no-shadow to turn it off.
  • page vs. pagecontainer events demo
  • Changing file structure
  • testswarm
    • Need to find out where to start
      • Alex looking into
  • selectmenu
    • Native fall back is complicated. Needs different markup
jQuery UI Team

jQuery UI Team Meeting – Mar 05 2014

jQuery Core Team

jQuery Core Team Meeting – Mar 03 2014

Attending: DaveMethvin, rwaldron, m_gol, gibson042

link Wrap up on browser support in 1.12/2.2

  • Dave has draft blog post
  • Stop accepting new bug reports on these, close wontfix
  • Only fix severe regressions but leave patches in for 1.12 & 2.2
  • Sync with UI to remove IE 7 etc support there too
  • Still needs edits to clarify, want to prevent wails of protest
  • Changes won't come until 1.13, months away
  • We'll pull IE6/7, Safari 5.1, Opera 12.1x all at once in 1.13
  • per markelog, what about IE7 CV mode in IE8?

link $.fn.data API

  • Let's make a call on this, need to make 1.x and 2.x compat
  • What is the easiest & least disruptive behavior change?
  • I'm leaning towards 1.x behavior with minor changes
  • Conclusion: "Embrace HTML5" with one exception: Don't camelize objects that are extended into the data object
  • TODO: clean up docs for .data() to make things clearer

link Bower

link support.boxSizing - why is the test so complicated & requires a body?

  • check old Androids
  • ask mikesherov

link 1.11.1 and 2.1.1

  • Land fixes soon so we can move on to 1.12 and 2.2 in master
  • Can always branch later if we need 1.11.2 etc

link Current open tickets