Closed Bug 314061 Opened 19 years ago Closed 4 months ago

Make Camino document-based for applescript

Categories

(Camino Graveyard :: OS Integration, enhancement)

PowerPC
macOS
enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE
Future

People

(Reporter: chris, Assigned: peeja)

References

Details

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en) AppleWebKit/412.7 (KHTML, like Gecko) Safari/412.5
Build Identifier: 1.0a1

------- Comment #16 From chris 2005-10-27 09:16 PDT [reply] -------
For comparison:
tell application "Safari"
  tell document 1
    set the clipboard to URL as string
  end tell
end tell

Works in safari, does not work in Camino. Trying to make the URL into a string
Fails during running. Getting rid of the "as string" allows it to run, but it
does not seem to copy the URL.

I think the "window #" construct is fine. Having scripts that run the same in
safari or Camino would be great.

------- Comment #17 From Simon Fraser 2005-10-27 09:27 PDT [reply] -------
Camino is not document based, so that's not going to work.

Ideally we would be, and perhaps expose multiple tabs per window via a one to
many document to window mapping or something.

Reproducible: Always
Summary: Consider making Camino document based for applescript access to tabs → Make Camino document based for applescript access to tabs
This is a carryover from bug 253486. Confirming (based on smfr's comments, targetting for future, and CCing smfr.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Target Milestone: --- → Future
*** Bug 326133 has been marked as a duplicate of this bug. ***
> ------- Comment #17 From Simon Fraser 2005-10-27 09:27 PDT [reply] -------
> Camino is not document based, so that's not going to work.
> 
> Ideally we would be, and perhaps expose multiple tabs per window via a one to
> many document to window mapping or something.

Or perhaps use the term 'tabs' instead of document, then. OmniWeb's AppleScript implementation really covers this well (only browser so far that covers it at all). If you want to look through dictionaries without needing the app, you can go to http://macscripter.net/app_dictionaries/
I'd totally go for 'tabs'.
I think we should make the dictionary access a little more ui-agnostic. There may be other ways in future that you could have > 1 browser per window.
Blocks: 380580
Blocks: 156078
No longer blocks: 380580
Taking, assuming we're not actually planning to make Camino document-based, as part of Summer of Code:
http://wiki.caminobrowser.org/Development:Summer_of_Code_2007:AppleScript

Right now, I've got browser windows which have tabs which have URLs and titles.  Browser windows also implicitly have the URL and title of their visible tab.

@Simon: If that comes up in the future, we can easily change the terminology and not break anyone's scripts.

More: https://bugzilla.mozilla.org/show_bug.cgi?id=253486#c27
Assignee: mikepinkerton → peter.a.jaros
Are we going to stay non-document-based, and either FIXED this based on 385989 proving access to tabs or WONTFIX based on staying non-document-based, or leave this Future for becoming document-based at some point (and kill tabs from the summary)?
Anyone object to marking this WONTFIX now that bug 385989 is complete? It might be nice to have two different ways to access URL in Camino with scripts, but can we live with one that works?
QA Contact: os.integration
Summary: Make Camino document based for applescript access to tabs → Make Camino document-based for applescript
Status: NEW → RESOLVED
Closed: 4 months ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.