[Webkit-unassigned] [Bug 49723] Expose default value of maxLength in Chromium API

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu Nov 18 15:27:08 PST 2010


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





--- Comment #10 from Ilya Sherman <isherman at chromium.org>  2010-11-18 15:27:08 PST ---
(From update of attachment 74286)
View in context: https://bugs.webkit.org/attachment.cgi?id=74286&action=review

>> WebKit/chromium/public/WebInputElement.h:84
>> +        WEBKIT_API static const int defaultMaxLength;
> 
> It is better to make this a function.
> The hard limit value might be platform-dependent in the future.

I'm confused -- why would a function be better than a constant in the face of platform dependencies?  I'm probably overlooking something, but it makes more sense to me to leave this as a constant and update it if/when the underlying WebKit implementation changes.

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



More information about the webkit-unassigned mailing list