<div class="gmail_quote">On Fri, Mar 25, 2011 at 1:08 PM, Peter Kasting <span dir="ltr"><<a href="mailto:pkasting@google.com">pkasting@google.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="gmail_quote"><div><div></div><div class="h5">On Fri, Mar 25, 2011 at 1:03 PM, Mark Rowe <span dir="ltr"><<a href="mailto:mrowe@apple.com" target="_blank">mrowe@apple.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word"><div><div></div><div><div><div>Safari 5.0.3 will always report a build version of 533.19.4. Safari 5.0.4 will always report a build version of 533.20.27. You already used the former in your "before examples".</div>
</div></div></div>
</div></blockquote><div><br></div></div></div><div>Ideally, I would like the Safari-on-Windows and Safari-on-Mac strings from a trunk build as of around the time my change landed, which I'd use as the identical before and after strings, and only change the portions actually affected by the UA changes that landed.</div>
</div></blockquote><div><br></div><div>Since this is slated for publication this morning, I checked with dglazkov and updated my draft to use the current UA strings from a ToT WebKit build. Hopefully now all the version numbers are sane and consistent.</div>
<div><br></div><div>PK</div></div>