[Android] Implement min/max on all supported date types

content/renderer/renderer_date_time_picker.cc

Index: content/renderer/renderer_date_time_picker.cc
diff --git a/content/renderer/renderer_date_time_picker.cc b/content/renderer/renderer_date_time_picker.cc
index f17ba3588be5d0001e42c594fbfdbd7875815389..5bc4e2a35d8947c25abf93d10b1dad777b639575 100644
--- a/content/renderer/renderer_date_time_picker.cc
+++ b/content/renderer/renderer_date_time_picker.cc
@@ -31,8 +31,6 @@ RendererDateTimePicker::~RendererDateTimePicker() {
 
 bool RendererDateTimePicker::Open() {
   DateTimeFormatter parser(chooser_params_);
-  std::string test_s = chooser_params_.currentValue.utf8();
-
   ViewHostMsg_DateTimeDialogValue_Params message;
   message.year =  parser.GetYear();
   message.month =  parser.GetMonth();
@@ -41,7 +39,10 @@ bool RendererDateTimePicker::Open() {
   message.minute = parser.GetMinute();
   message.second = parser.GetSecond();
   message.dialog_type = parser.GetType();
-
+  if (chooser_params_.minimum > 0)

[bulach, 2013/05/30 14:16:30]

iirc, the ViewHostMsg_DateTimeDialogValue_Params members are not zero
initialized, so message.minimum / maximum would potentially end up with
undefined data in the other end.. so, is this if necessary?

[Miguel Garcia, 2013/06/03 13:08:58]

Good point, let's better be safe than sorry here.

On 2013/05/30 14:16:30, bulach wrote:

+    message.minimum = chooser_params_.minimum;
+  if (chooser_params_.maximum > 0)
+    message.maximum = chooser_params_.maximum;
   Send(new ViewHostMsg_OpenDateTimeDialog(routing_id(), message));
   return true;
 }