4252 - [PI] Platform integration work on Mac

Status: RESOLVED INCOMPLETE

(Core Graveyard :: Tracking, defect, P3)

Description

[Simon Fraser [no longer active]]

I'm filing this bug to track the platform-specific work needed on Mac, as
first described in <news://news.mcom.com/sfraser-1503991611390001@h-208-12-39-
138.mcom.com>

Here's a stab at enumerating the Mac-specific features that
we'd like to have in Mozilla 5.0. Note that inclusion on this
list is not a commitment to include a certain feature in
the product.

I'm sure I've missed a ton of stuff here. Additions welcome.

Essential
---------

Note that some of these are really basic. I'm trying to make
an exhaustive list.

Here's a useful checklist:
<http://developer.apple.com/technotes/tn/tn1126.html>

Basic app functionality:
    BNDL resource, file types & icons for some set of file types
    Set BNDL bits correctly
    Various resources: 'hfdr', 'vers', 'open', 'kind'
    Gestalt test for system version, available features.
    Weak link with less common libs, and put up appropriate alerts when
        features are missing.

Event handling:
    Handle high level and disk events

Windows:
    Smart window sizing, working zoom
    Smart window positioning (multi-screen aware)

Menus:
    Apple & application menus  ;-)
    Appropriate use of help menu
    Shared menus support

AppleEvents:
    Required AppleEvents (open, run, print, quit)
    GetURL AppleEvent
    TSM AppleEvent handling

Drag & drop:
    Accept and supply clipping files
    Dragging files into browser window
    Make correct shortcut files in MacOS 8.5

Network I/O:
    Behave well on dialup links, PPP.
    Handle PowerBook sleep etc.

Display Manager:
    Respond to screen resolution & depth changes

Internet Config:
    IC interaction needs to be specified. Use for file extension->type
    mapping? (how does this interact with MIME types?)

Nice to have
------------

AppleEvents:
    Standard AppleEvents suite (basic scriptability, get at windows and
        their contents)
    'Execute JavaScript' AppleEvent

Translation Manager:
    'open' etc. resources, translate on open & save.
    QuickTime translations for images etc.

Folder Manager:
	Correct handling of Application Support folder. Store any items specific
	to application like libraries in System Folder:Application Support:Mozilla:

Comment 1

[Peter Trudelle]

We should really have separate bug reports for these, perhaps with a unique
string to ID them in the summary line as part of a group.  Multiple items in one
bug report is bad because it mixes up the issues and makes individual tracking
more difficult.

Comment 2

[Simon Fraser [no longer active]]

I was hoping that sdagley would break this up, and assign to appropriate
engineers. Sorry I forgot to put that in when I filed.

Comment 3

[Peter Trudelle]

assigning to sdagley as p3 for m4

Comment 4

[Simon Fraser [no longer active]]

Some more suggestions from the net:

Menus:
     Don't put version # or (tm) in the app name (for shorter name in the
          application menu). Allow app to run after renamed/moved
     True contextual menus (including plugin support)
     P.S. No more icon menus

Windows:
     Window proxy as Internet alias (may be non-standard or pioneering,
          check with Apple)
     Zoom rects? (for New Window with this Link)

Drag & drop:
     > Make correct shortcut files in MacOS 8.5
     The converse should be true also. Moz should handle opening
          multiple Internet aliases in Finder (including double-click,
          drag to app icon, drag to window).
     Maintain background selection (when Moz is inactive) and allow
          direct dragging from background to foreground

Network I/O:
     >Behave well on dialup links, PPP
     Non-modal dialing ala Eudora?

Help:
     Balloon help or equivalent in dialogs

Internet Config:
     Register with IC for appropriate protocols by user choice (obviously)

Comment 5

[Steve Dagley]

M4?  Definitely not going to make it.

Comment 6

[Steve Dagley]

Not an M6 blocker so moving to M7 to get it off the M6 radar.  That and the exact
set of Mac specific features is still being wrangled with so this bug will
eventually turn into scheduled tasks spread across several milestones.

Comment 7

[leger]

Moving all Apprunner bugs past and present to Other component temporarily whilst
don and I set correct component.  Apprunner component will be deleted/retired
shortly.

Comment 8

[Steve Dagley]

Sliding to M10 where I'll break this out into individual distributed bugs rather
than having just one assigned to myself.

Comment 9

[Steve Dagley]

Using new [PI] tag for Platform Integration rather than Platform Parity which has
a different connotation in my mind, started breaking out specific tasks we
_really_ want to address and added these bugs as dependencies, moved to M14 as
these aren't requirments for what we're currently referring to as "beta"

Comment 10

[Steve Dagley]

Moving this tracking bug to M15 (the dependancies were already moved)

Comment 11

[Peter Trudelle]

adding meta keyword

Comment 12

[Steve Dagley]

Moving this meta bug to M18 as it doesn't sound like there's any bodies to 
address this before beta2

Comment 13

[Pierre Saslawsky]

Bug 33527 ("MacOS Appearance Manager tracking bug") will be closed as dup of this 
one. I'm transfering the bug dependencies (1004,3371,16277).

Comment 14

[Pierre Saslawsky]

*** Bug 33527 has been marked as a duplicate of this bug. ***

Comment 15

[Oliver Klee]

Milestone 0.8 has been released. We should either resolve this bug or update its
milestone.

Comment 16

[Steve Dagley]

meta bug - no TFV

Comment 17

[Steve Dagley]

Since I don't report into Internet Technologies anymore this bug needs a new
owner -> saari

Comment 18

[louis bennett]

-> os x

Comment 19

[Andrea Govoni]

Shouldn't the Platform field be changed from "PowerPC Mac OS X" to only "Mac OS X"?

Comment 20

[BMO Automation]

Marking all tracking bugs which haven't been updated since 2014 as INCOMPLETE.
If this bug is still relevant, please reopen it and move it into a bugzilla component related to the work
being tracked. The Core: Tracking component will no longer be used.