[Webkit-unassigned] [Bug 46559] [chromium] Refactor ChromiumDataObject to use getters/setters.

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=46559





--- Comment #13 from Tony Chang <tony at chromium.org>  2010-09-30 10:40:02 PST ---
(In reply to comment #12)
> > FWIW, I preferred having ClipboardDataType since it's clear whether or not normalization has occurred yet.  I don't feel strongly about this, but it would be nice if we had a test case for the "text/plain;" normalization (I suspect on Windows if you're copying text in a different encoding, you might hit this).
> > 
> 
> In the future, we need to handle arbitrary strings. We could still use ClipboardDataType, but that means we'd need a getData() that takes a ClipboardDataType and another that takes a string.

Ah, that's a good point.  Maybe we should have setData and getData both normalize the string so callers don't have to?  That's how it used to work, right?  I'm just worried about callers forgetting to normalize.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.