calculateUTCOffset()/calculateDSTOffset these two function has been made static in changelist http://trac.webkit.org/changeset/150833 Using these function in other file is wrong and will give compile time error. Instead calculateLocalTimeOffset should be used.
Created attachment 209047 [details] Patch
Created attachment 209052 [details] Patch
Comment on attachment 209052 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=209052&action=review > Source/WebCore/ChangeLog:7 > + Resolving code error. What kind of code error? I don’t understand the reason behind this change. Is this more elegant? More correct? Both? If more correct, was there a test that was failing?
Comment on attachment 209052 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=209052&action=review >> Source/WebCore/ChangeLog:7 >> + Resolving code error. > > What kind of code error? I don’t understand the reason behind this change. Is this more elegant? More correct? Both? If more correct, was there a test that was failing? Oh, I see, you mean this resolves a build failure? Got it.
(In reply to comment #4) > (From update of attachment 209052 [details]) > View in context: https://bugs.webkit.org/attachment.cgi?id=209052&action=review > > >> Source/WebCore/ChangeLog:7 > >> + Resolving code error. > > > > What kind of code error? I don’t understand the reason behind this change. Is this more elegant? More correct? Both? If more correct, was there a test that was failing? > > Oh, I see, you mean this resolves a build failure? Got it. Right, Build will fail when input type date/time/month is enabled.
Comment on attachment 209052 [details] Patch Clearing flags on attachment: 209052 Committed r154315: <http://trac.webkit.org/changeset/154315>
All reviewed patches have been landed. Closing bug.