[email protected] said:
> Chrome is not an X client. It interacts with the screen via the API
> supplied by the OS. Why in the world would Chrome write to
> or read from that socket? How would it even know it exists?
I don't recall if this has been said, but I've seen this behavior with
other browsers besides Chrome. It happens for me with Firefox and Safari,
and possibly Opera as well. It may happen with other things (e.g., Adium,
Word, and Excel), but I'm not certain.
This has been happening for years for me, not just in the most recent
couple of versions.
Wayne Morrison
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/x11-users/archive%40mail-archive.com
This email sent to [email protected]
