Bug 55359

Summary: WebCore::Editor::selectionStartCSSPropertyValue crashes is no font size is supplied
Product: WebKit Reporter: Berend-Jan Wever <skylined>
Component: HTML EditingAssignee: Nobody <webkit-unassigned>
Status: RESOLVED DUPLICATE    
Severity: Normal CC: rniwa
Priority: P1    
Version: 528+ (Nightly build)   
Hardware: PC   
OS: Windows Vista   
Attachments:
Description Flags
Repro none

Berend-Jan Wever
Reported 2011-02-28 02:35:53 PST
Created attachment 84034 [details] Repro Chromium: http://code.google.com/p/chromium/issues/detail?id=74392 Variation of: bug 45068 Repro: <script>document.queryCommandValue("FontSize")</script> id: chrome.dll!WebCore::Editor::selectionStartCSSPropertyValue ReadAV@NULL (07e9b856f4be9e9f44daffbf76cc4066) description: Attempt to read from unallocated NULL pointer+0x4 in chrome.dll!WebCore::Editor::selectionStartCSSPropertyValue stack: chrome.dll!WebCore::Editor::selectionStartCSSPropertyValue chrome.dll!WebCore::valueFontSize chrome.dll!WebCore::Editor::Command::value chrome.dll!WebCore::Document::queryCommandValue chrome.dll!WebCore::DocumentInternal::queryCommandValueCallback chrome.dll!v8::internal::HandleApiCallHelper<...> chrome.dll!v8::internal::Builtin_HandleApiCall chrome.dll!v8::internal::Invoke chrome.dll!v8::internal::Execution::Call ...
Attachments
Repro (56 bytes, text/html)
2011-02-28 02:35 PST, Berend-Jan Wever
no flags
Ryosuke Niwa
Comment 1 2011-02-28 02:41:07 PST
I think this is a duplicate of https://bugs.webkit.org/show_bug.cgi?id=55290. *** This bug has been marked as a duplicate of bug 55290 ***
Berend-Jan Wever
Comment 2 2011-02-28 03:01:18 PST
Sorry Ryosuke - I only scanned Chromium bugs for duplicates and didn't find one. I'll make sure to scan both issue trackers in the future.
Ryosuke Niwa
Comment 3 2011-02-28 03:12:02 PST
(In reply to comment #2) > Sorry Ryosuke - I only scanned Chromium bugs for duplicates and didn't find one. I'll make sure to scan both issue trackers in the future. Nah, it's okay. Thanks a lot for always filing bugs :D.
Note You need to log in before you can comment on or make changes to this bug.