[TIMOB-10108] MobileWeb: Ti.API.log INFO level messages do not display as correct type

GitHub Issue	n/a
Type	Sub-task
Priority	Low
Status	Closed
Resolution	Fixed
Resolution Date	2013-08-20T21:14:49.000+0000
Affected Version/s	Release 2.1.0, Release 2.1.1
Fix Version/s	2013 Sprint 17, 2013 Sprint 17 Tooling, Release 3.1.3, Release 3.2.0
Components	MobileWeb
Labels	core, qe-mw070112
Reporter	Dustin Hyde
Assignee	Bryan Hughes
Created	2012-07-23T19:48:34.000+0000
Updated	2013-08-23T09:46:33.000+0000

Description

Ti.API.log messages show as [LOG] level instead of the log type passed in as the first argument. This is either an API or a documentation issue. Screenshots attached. This is not a regression. Steps to Reproduce: 1. Create app with code:

alert('SESSION ID: ' + Ti.App.sessionId);
Ti.API.error('SESSION ID: ' + Ti.App.sessionId);
Ti.API.trace('1A. TRACE');
Ti.API.log('TRACE', '1B. TRACE');
Ti.API.debug('2A. DEBUG');
Ti.API.log('DEBUG', '2B. DEBUG');
Ti.API.info('3A. INFO');
Ti.API.log('INFO', '3B. INFO');
Ti.API.warn('4A. WARN');
Ti.API.log('WARN', '4B. WARN');
Ti.API.error('5A. ERROR');
Ti.API.log('ERROR', '5B. ERROR');

2. Preview in MobileWeb Browser. 3. Open the console view in the browser (command + option + i in chrome os x). Actual Result: [LOG] level messages appear. Expected Result: [ERROR], [WARN], [TRACE], [DEBUG], and [INFO] messages should appear, based on the first argument of Ti.API.log().

Attachments

File	Date	Size
Android Log Levels.png	2012-07-23T19:48:34.000+0000	54342
iOS Log Levels.png	2012-07-23T19:48:34.000+0000	44449
MobileWeb Log Levels.png	2012-07-23T19:48:34.000+0000	57088

Comments

Christian Sullivan 2013-03-29

[MASTER] Pull Request: https://github.com/appcelerator/titanium_mobile/pull/4057
Bryan Hughes 2013-08-20

PR: https://github.com/appcelerator/titanium_mobile/pull/4584
Bryan Hughes 2013-08-20

3_1_X PR: https://github.com/appcelerator/titanium_mobile/pull/4586
Dhirendra Jha 2013-08-23

Test Environments - Appcelerator Studio: 3.1.3.201308201707 Titanium SDK: 3.1.3.v20130822140128 acs: 1.0.6 alloy: 1.2.1-cr npm: 1.3.2 titanium: 3.1.2 titanium-code-processor: 1.0.2 Web Browser: Chrome (29.0.1547.57) Result - Message appears as mentioned in the expected result. Hence closing this issue.

JSON Source