RESOLVED FIXED 24720
<input type="range"> invisible in Chromium port
https://bugs.webkit.org/show_bug.cgi?id=24720
Summary <input type="range"> invisible in Chromium port
Peter Kasting
Reported 2009-03-20 11:20:05 PDT
I need to add appropriate functions to RenderThemeChromiumWin.cpp.
Attachments
patch v1 (6.93 KB, patch)
2009-03-20 11:32 PDT, Peter Kasting
fishd: review-
patch v2 (7.74 KB, patch)
2009-03-20 18:25 PDT, Peter Kasting
fishd: review+
Peter Kasting
Comment 1 2009-03-20 11:32:31 PDT
Created attachment 28790 [details] patch v1 This patch also does a little reordering in one of the switches to put parts in numerical order.
Darin Fisher (:fishd, Google)
Comment 2 2009-03-20 16:48:47 PDT
Comment on attachment 28790 [details] patch v1 >Index: WebCore/rendering/RenderThemeChromiumWin.cpp >+bool RenderThemeChromiumWin::paintSliderTrack(RenderObject* o, const RenderObject::PaintInfo& i, const IntRect& r) >+{ >+ const ThemeData& themeData = getThemeData(o); >+ >+ WebCore::ThemePainter painter(i.context, r); >+ ChromiumBridge::paintTrackbar(painter.context(), Looks like you forgot to include your changes to ChromiumBridge in this patch. > case ListboxPart: > case MenulistPart: > case SearchFieldPart: > case TextFieldPart: > case TextAreaPart: >- result.m_part = ETS_NORMAL; >+ result.m_part = EP_EDITTEXT; what is the reason for this change?
Peter Kasting
Comment 3 2009-03-20 18:22:51 PDT
Sorry, will add ChromiumBridge.h. (The .cpp file is only in the Chrome tree, it looks like?) The EP_EDITTEXT change is because ETS_NORMAL is a state, not a part. EP_EDITTEXT is a part. They're both defined to 1 under the hood.
Peter Kasting
Comment 4 2009-03-20 18:25:45 PDT
Created attachment 28814 [details] patch v2
Peter Kasting
Comment 5 2009-03-23 12:04:23 PDT
Fixed in r41915.
Note You need to log in before you can comment on or make changes to this bug.