Closed GoogleCodeExporter closed 8 years ago
I have the same issue. I tried the latest Chromium build from 3/31 (5.0.367.0
(43218)) and so far it seems to be
working OK there.
Original comment by dpodwall
on 31 Mar 2010 at 7:21
Original comment by peter.ry...@gmail.com
on 1 Apr 2010 at 8:11
This should be a temporary issue. It should be fixed in the next build.
Original comment by peter.ry...@gmail.com
on 3 Apr 2010 at 3:59
You can check out the following table:
http://code.google.com/p/chromedevtools/wiki/VersionCompatibility
Original comment by peter.ry...@gmail.com
on 7 Apr 2010 at 5:37
Does this mean we would need to require our users to update the product as
Chrome gets
updated?
Original comment by eostrouk...@gmail.com
on 7 Apr 2010 at 5:41
This is only a recommendation. As a general practice the most recent version is
recommended.
In fact there might be a moment when future version of Chrome stops supporting
the
current protocol and old versions of plugins will stop working. However we
don't have
such plans for a near future AFAIK.
Original comment by peter.ry...@gmail.com
on 7 Apr 2010 at 5:58
I believe this one can be closed now - it works with the latest beta.
Original comment by eostrouk...@gmail.com
on 8 May 2010 at 12:26
Updated version for Mac works OK
Original comment by peter.ry...@gmail.com
on 9 Aug 2010 at 6:12
Original issue reported on code.google.com by
eostrouk...@gmail.com
on 26 Mar 2010 at 10:52