Bug 1374967 - Part 2: Consider step when deciding whether to show second/millisecond field. r=smaug

We should consider step and step base when deciding whether to show second and
millisecond field, since step and step base can affect the valid time intervals,
and the valid intervals may have second/millisecond part.

MozReview-Commit-ID: H4mJvLTvBOM

layout/forms/nsDateTimeControlFrame.cpp

@@ -55,7 +55,7 @@ nsDateTimeControlFrame::DestroyFrom(nsIFrame* aDestructRoot)
 }
 
 void
-nsDateTimeControlFrame::UpdateInputBoxValue()
+nsDateTimeControlFrame::OnValueChanged()
 {
   nsCOMPtr<nsIDateTimeInputArea> inputAreaContent =
     do_QueryInterface(mInputAreaContent);
@@ -64,6 +64,16 @@ nsDateTimeControlFrame::UpdateInputBoxValue()
   }
 }
 
+void
+nsDateTimeControlFrame::OnMinMaxStepAttrChanged()
+{
+  nsCOMPtr<nsIDateTimeInputArea> inputAreaContent =
+    do_QueryInterface(mInputAreaContent);
+  if (inputAreaContent) {
+    inputAreaContent->NotifyMinMaxStepAttrChanged();
+  }
+}
+
 void
 nsDateTimeControlFrame::SetValueFromPicker(const DateTimeValue& aValue)
 {