Issue metadata
Sign in to add a comment
|
The dropdowns are not showing values
Reported by
bhanu.ch...@roche.com,
Nov 2 2017
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.75 Safari/537.36 Steps to reproduce the problem: 1. Select a combobox div as attached in screenshot. 2. Click on drop down. 3. Nothing is displayed. 4. Try to inspect element and close, It appears somehow strangely after that. 5. Disappear after you close and try to open the form again. What is the expected behavior? Combobox should show the drop down values. What went wrong? The combobox widget looks broken. Did this work before? Yes 61 Chrome version: 62.0.3202.75 Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: It's a big bug for applications, Please fix this ASAP. Contact me at bhanucvbmg@gmail.com if you need a demo. PLEASE FIX ASAP.
,
Nov 2 2017
Standard HTML combobox (see [1]: SELECT and DATALIST) works without problems so in your case there's something else going on. You'll need to provide the URL exhibiting the problem or mock up a demo on jsfiddle.net Are there any relevant error messages in devtools console? [1]: http://jsfiddle.net/BobStein/ty640uva/
,
Nov 2 2017
Can we have a hangout/webex to show the issue? It's very critical, This is issue with HPSM Enterprise application which is very critcal.
,
Nov 2 2017
Waiting for a Chromium developer who can connect to your computer might take too long. I think it's better for you to ask your developers to use https://www.chromium.org/developers/bisect-builds-py That script downloads and runs pre-built Chromium snapshots and in the end prints a long changelog link that contains the change that's causing the bug.
,
Nov 2 2017
...use https://omahaproxy.appspot.com to obtain revision numbers e.g. for v61 - v62 range: python bisect-builds.py -a win64 -g 488528 -b 499098 -- http://your.app.url/
,
Nov 3 2017
//Below element on 62.0.3202.75 (Official Build) (64-bit). which is unexpected....as it should be hidden...which is creating issue.
<input reflabels="" buttonid="" dvdvar="var/hlrCiSelected" onkeydown="hpsm.widgets.Combo.keyDown(event, 'X21');" datachangeevent="" tabindex="" scripttype="combo" value="" id="X21" type="text" onkeyup="hpsm.widgets.Combo.keyUp(event, 'X21');" alias="var/hlrCiSelected" name="var/hlrCiSelected" role="combobox" aria-autocomplete="both" aria-owns="X21Popup_div" aria-activedescendant="X21Popup_div" aria-haspopup="true" aria-expanded="false" maxlength="" style="
height:18px;margin-top:1px;
" selectonly="1" onfocus="hpsm.widgets.Combo.handleOnFocus(this, event);" onblur="hpsm.widgets.Combo.handleOnBlur(this, event);" onclick="handleOnClick(this, event);" onchange="handleOnChange(this, event);">
//on 62.0.3202.75 We could see <input style="display:none;visibility:hidden;margin:0;padding:0;" id="X21Hidden" type="hidden" value=""> too
// Below element on 577.0.2987.133 or any other versions prior to 62.0.3202.75 are been hidden....which is working fine..
<div class="mandatoryFieldStyle xEdit file_joinsvcDisplay field_hlrCiSelected" style="height:20px;"><div class="xEditInner" style="height:100%;"><input reflabels="" buttonid="" dvdvar="var/hlrCiSelected" onkeydown="hpsm.widgets.Combo.keyDown(event, 'X21');" datachangeevent="" tabindex="" scripttype="combo" value="" id="X21" type="text" onkeyup="hpsm.widgets.Combo.keyUp(event, 'X21');" alias="var/hlrCiSelected" name="var/hlrCiSelected" role="combobox" aria-autocomplete="both" aria-owns="X21Popup_div" aria-activedescendant="X21Popup_div" aria-haspopup="true" aria-expanded="false" maxlength="" style="
height:18px;margin-top:1px;
" selectonly="1" onfocus="hpsm.widgets.Combo.handleOnFocus(this, event);" onblur="hpsm.widgets.Combo.handleOnBlur(this, event);" onclick="handleOnClick(this, event);" onchange="handleOnChange(this, event);"></div><div class="xButton" id="X21ButtonDiv" style=""><a draggable="false" class="image-link" aria-label="Expand List" tabindex="" href="javascript:hpsm.widgets.Combo.show('X21');void(0);"><img draggable="false" title="Expand List" alt="Expand List" src="images/comboup.png" id="X21Button"></a></div></div></div>
<input style="display:none;visibility:hidden;margin:0;padding:0;" id="X21Hidden" type="hidden" value=""
Could you please have a look into all the above scenarios and please fix the issue on prority ...Thank you.
,
Nov 3 2017
Bibin, can you please try a repro and bisect?
,
Nov 6 2017
Hello Team, Can we have update on this .....please treat it as High Priority as it s Impacting HPSM Application...Thank you. Regards, M Linga Reddy
,
Nov 6 2017
Unable to reproduce this issue on Windows-7 & 10 using chrome latest stable #62.0.3202.75 using the below test link http://docs.sencha.com/extjs/4.2.5/extjs-build/examples/form/combos.html. Observed able to see all the items in the list box and able to select the value as expected. Tested the same on some internal applications as well, still unable to reproduce the issue. malle.reddy@ Could you please provide any sample test case or test URL of your application to check this issue from Chrome-TE end? As per comment #4 and #5 are you able to perform bisect from your end? Thanks!
,
Nov 6 2017
Thank you for the update... Can we have WebEx session please...so that I can show how to replicate the issue. Regards, M Linga Reddy
,
Nov 6 2017
,
Nov 6 2017
Hello Mano/Raj, I will be available from 11:30 IST to 20:30 IST....or please let me know your convenient time to have a demo/discussion on this.Thank you. Regards, M Linga Reddy
,
Nov 6 2017
,
Nov 7 2017
Hello Mano, May I know the update please..Thank you. Regards, M Linga Reddy
,
Nov 8 2017
Unless reproducible test cases are available outside any proprietary product/site, we can never work on fix it.
,
Nov 8 2017
Hello Konchi, We have given details when exactly the issue is occurring in comment 6. Could you pleas check and let me know if you need any other info...Can we have hangout/Webex call to have a discussion on this..Thank you. Regards, M Linga Reddy
,
Nov 8 2017
snippet 1 is the total html
,
Nov 8 2017
snippet 2 is the sub element.
,
Nov 8 2017
You can run the jsfiddle against two, When ran seperately, snippet2 works, but with the total html, it's broken, it used to work before. Please FIX ASAP...
,
Nov 8 2017
Thank you for providing more feedback. Adding requester "brajkumar@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 9 2017
While opening the first test case file from comment #17 observed the page is completely broken and while opening the second test case file from comment #18 page loads perfectly. In the both the test cases am not seeing any combo boxes available to check the issue, observing similar behavior on Firefox browser as well. Not sure if this is a complete test case file where we can reproduce the actual issue, could you please provide a working test case to check this issue from Chrome-TE end? Thanks!
,
Nov 16 2017
After having an offline discussion with the reporter confirming this issue still persists on chrome latest stable M62. Observing some random mandatory drop down box in the page, and these drop down boxes doesn’t have any values to select. Due to this issue reporter is unable to submit any orders from their site and it was not seen on previous chrome stable #61.0.3163.100. Note: ----- 1. This issue is not reproducible on chrome latest beta M63 #63.0.3239.40. Attaching screen cast for reference. 2. Since this issue is not reproducible from our end, requested reporter to perform bisect using chromium builds and we got the below range as good and bad. Bisect Information: -------------------- Good build: 498335 Bad build: 498560 CL: https://chromium.googlesource.com/chromium/src/+log/afcc763ac1f0cec903036bfc1f61e05c8697bf01..bbf271c3e0989faf73fefd64b26a4625af1287dd Unable to find the actual suspect from the above CL due to multiple changes are available. Could someone look in to this issue? Thanks!
,
Nov 17 2017
M63 stable release is just ~two weeks (12/05) away, so i think we are all set here. bhanu.chaluvadi@, please feel free to update if you are seeing this issue with Chrome canary (https://www.google.com/chrome/browser/canary.html) Just in case. Thank you!
,
Nov 20 2017
Hi, Will test it after the official go-Live. Thanks for the help :)
,
Dec 7 2017
Hello Team, M63 stable release was not deployed on 05/12/2017....Could you please advise us when its going to be released.Thank you. Regards, M Linga Reddy
,
Dec 27 2017
M63 stable should have released public for 2-3 weeks. Maybe your corp IT is managing the Chrome update, but we cannot be sure.
,
Jan 17 2018
Reporter, did Chrome 63 fix this issue?
,
Jan 17 2018
Yes issue is resolved, Support is appreciated..
,
Jan 19 2018
,
Jan 31 2018
The NextAction date has arrived: 2018-01-31 |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by nyerramilli@chromium.org
, Nov 2 2017