Some scripts not working properly
Reported by
ole...@olegon.ru,
Feb 28 2016
|
|||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.109 Safari/537.36 Example URL: http://olegon.ru/ Steps to reproduce the problem: Click on edit link [правка] or Post message or Press Ctrl-B to bold font What is the expected behavior? Open edit window or Normal post the message or Insert [b] [/b] codes in editor window What went wrong? I need to click twice on link and get "Uncaught TypeError: Cannot read property 'wysiwyg_mode' of undefined" Sometimes message posted twice, and page jump upside [b] codes not works at all... Does it occur on multiple sites: N/A Is it a problem with a plugin? No Did this work before? Yes 46.0.2490.80-1.fc23.R.x86_64 Does this work in other browsers? Yes Chrome version: 48.0.2564.109 Channel: stable OS Version: Fedora Flash Version: Shockwave Flash 20.0 r0 This problem exists since chromium-47.0.2526.106-2.fc23.R.x86_64, when downgraded to 46.0.2490.80-1.fc23.R.x86_64 it's all ok again except [b] hotkeys. In Firefox and Chrome problem is not reproducing. Problem is stable at different machines, including Incognito.
,
May 2 2016
olegon@: Do you still see this issue on the latest stable(50.0.2661.94). If yes, could you please provide any test credentials to sign in and check the issues. Appreciate your response!
,
May 3 2016
thank you for attention! Please, visit https://olegon.ru/showthread.php?t=24534 (using username, I sent to you by email), scroll down to textarea with name vB_Editor_QR_textarea, and try to press Ctrl-B, Ctrl-I and Ctrl-U in it (may try with selection). It's no script error in console, but [b] and other is not appeared :( And in Mozilla browsers, even Midori (!) it works. This is standart VBulletin3 (forum) feature, so many sites is affected...
,
May 3 2016
Thank you for providing more feedback. Adding requester "ajha@chromium.org" for another review and adding "Needs-Review" label for tracking. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
May 9 2016
Able to reproduce this on the latest stable(50.0.2661.94) and the latest canary(52.0.2729.0) on Windows-7, Mac OS 10.11.4 and Linux Ubuntu 14.04. Selecting the text and Ctrl+B doesn't insert the [b] [/b] to the selected text. Same behavior is observed on the older chrome version: 30.0.1549.0. Marking this as Untriaged and attaching the screen-cast of the behavior from older chrome version.
,
Jun 1 2016
Moving this nonessential bug to the next milestone. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 15 2016
This issue has been moved once and is lower than Pri-1. Removing the milestone. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
May 29 2018
The problematic code in vbulletin is:
var A = C.charCode ? C.charCode : C.keyCode;
var B;
switch (String.fromCharCode(A).toLowerCase()) {
case "b":
B = "bold";
break;
case "i":
B = "italic";
break;
case "u":
B = "underline";
break;
default:
return
}
The problem is C.charCode returns '2' for Chrome and Edge whereas Firefox returns '98'. This is just fundamentally one of the problems with this attribute. KeyboardEvent.key was designed to replace it and should be used in vbulletin to avoid this interop difference between FireFox and Chrome, Edge.
|
|||||||||||
►
Sign in to add a comment |
|||||||||||
Comment 1 by ole...@olegon.ru
, Mar 12 2016