New issue
Advanced search Search tips

Issue 913363 link

Starred by 3 users
Status: Assigned
Owner:
einbinder@chromium.org
Cc:
phanindra.mandapaka@chromium.org
einbinder@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Bug



Sign in to add a comment

devTools: Date.parse has cssText as argument hint

Reported by jeromin....@gmail.com, Dec 10 
Chrome Version       : 72.0.3626.7
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
URLs (if applicable) :
Other browsers tested:
  Add OK or FAIL after other browsers where you have tested this issue:
     Safari: NA
    Firefox: NA
    IE/Edge: NA

What steps will reproduce the problem?
1. open DevTools
2. Type "Date.parse("

What is the expected result?
Since chrome 68 we have wonderful argument hints.
https://developers.google.com/web/updates/2018/05/devtools#hints
I would expect the argument name should be "dateString".

What happens instead of that?
The argument name is cssText

Please provide any additional information below. Attach a screenshot if
possible.

UserAgentString: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3626.7 Safari/537.36
chrome_devTools_tooltip_dateParse.png
2.3 KB View Download

Comment 1 by woxxom@gmail.com, Dec 10 

The feature was added in r558527.
AFAICT it scans IDL files but Date.parse is only defined as a V8 built-in [1].
The IDL files describe only CSSStyleValue.parse and CSSNumericValue.parse [2].

  [1]: https://cs.chromium.org/chromium/src/v8/src/builtins/builtins-date.cc?l=293&rcl=4bb7e4fa
  [2]: https://cs.chromium.org/search/?q=lang:idl+%5Cbparse%5C(+-file:test&sq=package:chromium&type=cs

Comment 2 by dtapu...@chromium.org, Dec 10

Components: Platform>DevTools

Comment 3 by susan.boorgula@chromium.org, Dec 10

Labels: Needs-Triage-M72

Comment 4 by binghamj@google.com, Dec 11

Components: -Platform>DevTools Platform>DevTools>JavaScript

Comment 5 by phanindra.mandapaka@chromium.org, Dec 20

Cc: einbinder@chromium.org phanindra.mandapaka@chromium.org
Labels: -Pri-3 Triaged-ET Target-73 M-73 FoundIn-71 FoundIn-73 FoundIn-72 OS-Linux OS-Mac Pri-2
Status: Untriaged (was: Unconfirmed)
As per comment #0, Able to reproduce the issue on reported chrome version 72.0.3626.7 also on latest chrome 73.0.3644.0 using Mac 10.14.0, Ubuntu 17.10 and Windows 10.  
 
As per comment # 1, same behavior is seen on M68(68.0.3432.0) hence marking it as Untriaged and CC'ing Dev (einbinder@chromium.org) for further investigation on it.

Thanks..!

Comment 6 by hhli@chromium.org, Jan 10

Owner: einbinder@chromium.org
Status: Assigned (was: Untriaged)
►

Sign in to add a comment