Open Bug 180625 Opened 22 years ago Updated 14 years ago

Text captured through Services Menu should retain formatting

Categories

(Camino Graveyard :: General, enhancement)

Product:
Camino Graveyard
Component:
General
Platform:
PowerPC
macOS
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
REOPENED
Milestone:
Future

People

(Reporter: Saarinen, Unassigned)

References

Details

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.0.1) Gecko/20021117 Chimera/0.6+
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.0.1) Gecko/20021117 Chimera/0.6+

When capturing text from a web page through the Services Menu, the text should
retain the same formatting it had in the web page (font, color, size, etc). Text
captured right now defaults to Courier with hard returns at the end of each line
(PC formatting). The best example I can give for how it should work is OmniWeb.
Text captured thought the Services Menu in OW wraps to the page and maintains
all formatting as if you were looking at it on the web page 

Reproducible: Always

Steps to Reproduce:
1. Select text from any web page
2. Go to Navigator/Services/TextEdit/Open Selection

Actual Results:  
Text is generically formatted

Expected Results:  
Text should appear as it does on the web page and wrap to the page (Mac Formatting)
Yup.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Ugh, doing styled text would be really hard. We don't have any built-in support
to convert from Gecko's text layout to Cocoa styled text.
Assignee: saari → sfraser
Target Milestone: --- → Future
*** Bug 188903 has been marked as a duplicate of this bug. ***
How does Safari manage this task? Is there any crossover to what is needed to
accomplish the job in Chimera?
Flags: camino0.9?
Denying request for this to block 0.9. Marking 1.0 so we look at it again after
the release.
Flags: camino0.9? → camino0.9-
Target Milestone: Future → Camino1.0
this is a dupe of a ancient gecko bug that we futured (or WONTFIXd) ages ago.
doing the styled text conversion is non-trivial and very low on our priority list.
This should not block 1.0. Per Mike in comment 7, targeting to FUTURE.
Target Milestone: Camino1.0 → Future
*** Bug 326336 has been marked as a duplicate of this bug. ***
Duping. If this isn't the right dupe, please re-open and re-dupe appropriately, but I'm pretty sure this is it.

cl

*** This bug has been marked as a duplicate of 79864 ***
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
That's a really messy bug, but in the end it seems to be the right one, as long as Services automatically picks up the formatting when, in 10 years, the Core bug is fixed.
Status: RESOLVED → VERIFIED
I'm not completely sure we need the Core rich/HTML clipboard text support to do this, as it looks like our Services code really uses its own codepath (it can fetch HTML right now, were we to tell it to, though I can't figure out how to tell it to emit HTML-as-HTML rather than HTML-as-plain-text).

See http://bonsai.mozilla.org/cvsblame.cgi?file=mozilla/camino/src/embedding/CHBrowserView.mm&rev=1.113&mark=1712#1712 and bug 196704 comment 8.
Status: VERIFIED → REOPENED
Resolution: DUPLICATE → ---
Assignee: sfraser_bugs → nobody
QA Contact: winnie → general
= See also =

bug 470642

----------------------------------------------------------------------------
           Summary|System Services             |Send rich text to Mac OS X
                  |(interapplication           |Services
                  |communication on Mac OS X): |
                  |provider services to        |
                  |support richer text in      |
                  |Mozilla applications        |
Albert (reporter) and all: 

1. I suggest a change for this bug 180625 
from Platform: PowerPC Mac OS X
to Platform: All Mac OS X.

2. might this bug 180625 be changed 
from Product: Camino 
to Product: Core?
You need to log in before you can comment on or make changes to this bug.