Custom Query (18300 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (118 - 120 of 18300)

Ticket Resolution Summary Owner Reporter
#18828 fixed [regression] "npm install" broken dylan bill
Description

Starting with 7f24d9a282d6ab1d222e17fec6f32394aef947f2, npm install is broken. (I'm running it because tests/README.md says I need to run it to run the tests.)

This is the output from that revision. The output on master is slightly different (looking for 1.12), but basically the same.

$ npm install
npm ERR! Darwin 14.5.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install"
npm ERR! node v4.2.6
npm ERR! npm  v3.7.1

npm ERR! No compatible version found: [email protected]
npm ERR! Valid install targets:
npm ERR! 2.0.0-alpha4, 2.0.0-alpha3, 2.0.0-alpha2, 2.0.0-alpha1, 2.0.0-alpha.7, 2.0.0-alpha.6, 2.0.0-alpha.5, 1.11.1, 1.11.0, 1.11.0-rc5, 1.11.0-rc4, 1.11.0-rc3, 1.11.0-rc1, 1.10.5, 1.10.4, 1.10.3, 1.10.2, 1.10.1, 1.10.0, 1.9.8, 1.9.7, 1.9.6, 1.9.5, 1.9.4, 1.9.3, 1.9.2, 1.9.1
npm ERR! 
npm ERR! 
npm ERR! If you need help, you may report this error at:
npm ERR!     <https://github.com/npm/npm/issues>

npm ERR! Please include the following file with any support request:
npm ERR!     /ibm-js/dojo/npm-debug.log
#18827 invalid Traditional/simplified translations mixed up in com.ibm.ia.admincenter/WebContent/js/dojo_1.10.4/gidx/nls. rlejeune
Description

Language: T-Chinese ===================================================== Problem description: The string "No items to display" displayed in S-Chinese when we access AdminCenter? in T-Chinese locale ===================================================== PII info: No corresponding PII found but this string has translation - I assume it is 3rd party string. ===================================================== Expected result: The string should display proper locale translation

dojo gridx component. The translation files can be found in com.ibm.ia.admincenter/WebContent/js/dojo_1.10.4/gidx/nls. There are gridx.js files in each of the i18n directories including zh and zh-tw. I am not sure if one of those has the right translation.

#18826 fixed dojo/parser confused by Node.rootNode bill Jeremiah Orr
Description

Support for Node.rootNode recently showed up in Chrome Canary (I'm on version 51.0.2699.0). This confuses dojo/parser.parse(), as it thinks that if the first argument has a rootNode property, it must be the options hash instead of a DOM node. The problem code is here: https://github.com/dojo/dojo/blob/master/parser.js#L873-L875

Now that it thinks rootNode is actually an options object, it looks to arguments[0].rootNode for where to begin parsing (instead of just arguments[0]). Since Node.rootNode returns the document root, it parses the entire document.

To see this in action, check out http://codepen.io/orr94/pen/EKbKeM in both Chrome and Canary. In Chrome, you'll see that only the first input element is parsed and turned into a Dijit widget, as expected. In the current version of Canary, you'll see that both inputs are parsed and turned into widgets.

Note: See TracQuery for help on using queries.