On Tue, Dec 4, 2012 at 3:26 PM, Ryosuke Niwa <rn...@webkit.org> wrote:
> On Tue, Dec 4, 2012 at 1:32 AM, Arunprasad Rajkumar < > ararunpra...@gmail.com> wrote: > >> Thanks for your good explanation. But none of the ports providing SVN >> version information in either UA (or) navigator object. Anyhow it is upto >> them. >> > > That's because it's not meaningful to do. When a vendor decides to release > a Web browser based on a particular revision of WebKit, the vendor normally > creates a branch at that revision and then merges regression, security, and > other important fixes into the branch. It could even revert a revision in > that branch. WebKit also has various build flags that allows vendors to > enable or disable features at compilation time. Because of these two > modifications vendors can make to WebKit, two Web browsers based on a > WebKit revision X where X is some integer can have different set of > features, bug fixes, and bugs. > > Yeah very good explanation. For chrome, you can try chrome://version/ which is just an indicative revision (as pointed by R. Niwa i.e. X revision) that was picked up inside building the chrome. But this is just for the reference revision number. It will have a lot of other missing pieces added as mentioned above. - R. Niwa > > > _______________________________________________ > webkit-help mailing list > webkit-help@lists.webkit.org > http://lists.webkit.org/mailman/listinfo/webkit-help > >
_______________________________________________ webkit-help mailing list webkit-help@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-help
