| Summary | obrowser can't get current window name |
| Queue | Whups |
| Queue Version | Git master |
| Type | Bug |
| State | Not A Bug |
| Priority | 1. Low |
| Owners | |
| Requester | birnbacs (at) gmail (dot) com |
| Created | 10/12/2015 (3615 days ago) |
| Due | |
| Updated | 11/24/2015 (3572 days ago) |
| Assigned | |
| Resolved | 11/24/2015 (3572 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
State ⇒ Not A Bug
support with a generic attribute support. This is one of those.
State ⇒ Unconfirmed
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ obrowser can't get current window name
Queue ⇒ Whups
Milestone ⇒
Patch ⇒ No
not function as they are shipped. It would be nice to have all
available attribute types tested in the upcoming release.
obrowser, for instance, keeps complaining "invalid window name
supplied" when pointed to a resource. This is a real pity as it is a
powerful and interesting attribute that may be useful to many.
The bug may be related to a browser suppressing popup windows. I am
useing firefox and specifically allowed popou windows for the Horde
server. I get one more tab and one popup window, both of which behave
the same.
obrowser is making extensive use of JavaScript (via Ajax) so debugging
will best be left to those who developed it.