|
|
DescriptionHTMLOptionElement constructor arguments default
values are not per spec
As per spec link:
https://html.spec.whatwg.org/#the-option-element,
default value for selected attribute is false.
BUG=460722
Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=197930
Patch Set 1 #
Total comments: 2
Patch Set 2 : #
Total comments: 1
Messages
Total messages: 36 (18 generated)
shiva.jm@samsung.com changed reviewers: + pdr@chromium.org, philipj@opera.com
pls have a look.
Thanks, this LGTM, but remove the text if some existing test covers it. If you look at how the generated code changes, is there any way at all this change is observable? I suspect that it is not. https://codereview.chromium.org/1203943002/diff/1/LayoutTests/fast/dom/HTMLOp... File LayoutTests/fast/dom/HTMLOptionElement/option-constructor.html (right): https://codereview.chromium.org/1203943002/diff/1/LayoutTests/fast/dom/HTMLOp... LayoutTests/fast/dom/HTMLOptionElement/option-constructor.html:2: <script src="../../../resources/js-test.js"></script> I think some of the existing tests should cover this, please grep for 'new Option' to see if there's anything that isn't covered and if so modify an existing test, perhaps one of: fast/forms/option-constructor-selected.html fast/js/custom-constructors.html
Updated the review comments. pls have a look. https://codereview.chromium.org/1203943002/diff/1/LayoutTests/fast/dom/HTMLOp... File LayoutTests/fast/dom/HTMLOptionElement/option-constructor.html (right): https://codereview.chromium.org/1203943002/diff/1/LayoutTests/fast/dom/HTMLOp... LayoutTests/fast/dom/HTMLOptionElement/option-constructor.html:2: <script src="../../../resources/js-test.js"></script> On 2015/06/24 09:08:56, philipj wrote: > I think some of the existing tests should cover this, please grep for 'new > Option' to see if there's anything that isn't covered and if so modify an > existing test, perhaps one of: > fast/forms/option-constructor-selected.html > fast/js/custom-constructors.html Done.
The CQ bit was checked by shiva.jm@samsung.com to run a CQ dry run
The patchset sent to the CQ was uploaded after l-g-t-m from philipj@opera.com Link to the patchset: https://codereview.chromium.org/1203943002/#ps20001 (title: " ")
The CQ bit was unchecked by shiva.jm@samsung.com
The CQ bit was checked by shiva.jm@samsung.com to run a CQ dry run
The CQ bit was unchecked by shiva.jm@samsung.com
The CQ bit was checked by shiva.jm@samsung.com
The CQ bit was unchecked by shiva.jm@samsung.com
The CQ bit was checked by shiva.jm@samsung.com to run a CQ dry run
The CQ bit was checked by shiva.jm@samsung.com
The CQ bit was unchecked by shiva.jm@samsung.com
The CQ bit was checked by shiva.jm@samsung.com
The CQ bit was unchecked by shiva.jm@samsung.com
The CQ bit was checked by shiva.jm@samsung.com to run a CQ dry run
The CQ bit was unchecked by shiva.jm@samsung.com
The CQ bit was checked by shiva.jm@samsung.com to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1203943002/20001
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: This issue passed the CQ dry run.
On 2015/06/24 09:08:56, philipj wrote: > Thanks, this LGTM, but remove the text if some existing test covers it. If you > look at how the generated code changes, is there any way at all this change is > observable? I suspect that it is not. > > https://codereview.chromium.org/1203943002/diff/1/LayoutTests/fast/dom/HTMLOp... > File LayoutTests/fast/dom/HTMLOptionElement/option-constructor.html (right): > > https://codereview.chromium.org/1203943002/diff/1/LayoutTests/fast/dom/HTMLOp... > LayoutTests/fast/dom/HTMLOptionElement/option-constructor.html:2: <script > src="../../../resources/js-test.js"></script> > I think some of the existing tests should cover this, please grep for 'new > Option' to see if there's anything that isn't covered and if so modify an > existing test, perhaps one of: > fast/forms/option-constructor-selected.html > fast/js/custom-constructors.html Dry run has passed for patch set2, shall we commit this patch2?
Message was sent while issue was closed.
Apologise by mistake clicked on the closed button.
Message was sent while issue was closed.
Apologise by mistake clicked on the closed button.
LGTM. Please reference a bug or remove the empty BUG= before sending to CQ. https://codereview.chromium.org/1203943002/diff/20001/LayoutTests/fast/js/scr... File LayoutTests/fast/js/script-tests/custom-constructors.js (right): https://codereview.chromium.org/1203943002/diff/20001/LayoutTests/fast/js/scr... LayoutTests/fast/js/script-tests/custom-constructors.js:46: shouldBeFalse("new Option('somedata', 'somevalue', false, false).defaultSelected"); I don't think testing that the |selected| argument doesn't influence |defaultSelected| is necessary, but the bots are happy now and it's just some extra paranoia, so let's land this :)
(Also wrap description to 72 columns.)
(Also wrap description to 72 columns.)
On 2015/06/26 14:28:38, philipj wrote: > LGTM. Please reference a bug or remove the empty BUG= before sending to CQ. > > https://codereview.chromium.org/1203943002/diff/20001/LayoutTests/fast/js/scr... > File LayoutTests/fast/js/script-tests/custom-constructors.js (right): > > https://codereview.chromium.org/1203943002/diff/20001/LayoutTests/fast/js/scr... > LayoutTests/fast/js/script-tests/custom-constructors.js:46: shouldBeFalse("new > Option('somedata', 'somevalue', false, false).defaultSelected"); > I don't think testing that the |selected| argument doesn't influence > |defaultSelected| is necessary, but the bots are happy now and it's just some > extra paranoia, so let's land this :) Thanks Done.
The CQ bit was checked by shiva.jm@samsung.com
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1203943002/20001
Message was sent while issue was closed.
Committed patchset #2 (id:20001) as https://src.chromium.org/viewvc/blink?view=rev&revision=197930
Message was sent while issue was closed.
In this CL you accidentally removed the first line from the description. I've made the same mistake, and it means that the resulting commit doesn't have a good description.
Message was sent while issue was closed.
On 2015/07/01 11:40:16, philipj wrote: > In this CL you accidentally removed the first line from the description. I've > made the same mistake, and it means that the resulting commit doesn't have a > good description. I checked in the link: http://src.chromium.org/viewvc/blink/trunk/Source/core/html/HTMLOptionElement..., description/Log Message is visible fine. is the link i am looking is different ?.
Message was sent while issue was closed.
On 2015/07/01 11:56:59, shiva.jm wrote: > On 2015/07/01 11:40:16, philipj wrote: > > In this CL you accidentally removed the first line from the description. I've > > made the same mistake, and it means that the resulting commit doesn't have a > > good description. > > I checked in the link: > http://src.chromium.org/viewvc/blink/trunk/Source/core/html/HTMLOptionElement..., > description/Log Message is visible fine. is the link i am looking is different > ?. Oh, I wasn't paying attention, now I see what happened. The title was just wrapped to 72 columns (as I asked) and so it's split into two lines. No worries.
Message was sent while issue was closed.
On 2015/07/01 14:43:59, philipj wrote: > On 2015/07/01 11:56:59, shiva.jm wrote: > > On 2015/07/01 11:40:16, philipj wrote: > > > In this CL you accidentally removed the first line from the description. > I've > > > made the same mistake, and it means that the resulting commit doesn't have a > > > good description. > > > > I checked in the link: > > > http://src.chromium.org/viewvc/blink/trunk/Source/core/html/HTMLOptionElement..., > > description/Log Message is visible fine. is the link i am looking is different > > ?. > > Oh, I wasn't paying attention, now I see what happened. The title was just > wrapped to 72 columns (as I asked) and so it's split into two lines. No worries. These change was made to address FIX mes in HTML IDL files, these issue can be associated to bug: https://code.google.com/p/chromium/issues/detail?id=460722. may be its missed out in revision. |