This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 14068 - Think about what to return for backColor/hiliteColor value if it winds up being fully transparent
Summary: Think about what to return for backColor/hiliteColor value if it winds up bei...
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: HISTORICAL - HTML Editing APIs (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Aryeh Gregor
QA Contact: HTML Editing APIs spec bugbot
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-07 20:11 UTC by Aryeh Gregor
Modified: 2011-09-16 20:51 UTC (History)
2 users (show)

See Also:

Attachments

Description Aryeh Gregor 2011-09-07 20:11:01 UTC 
Currently the spec says to return rgb(255, 255, 255).  Maybe we should return rgba(0, 0, 0, 0) instead.  Have to check what browsers do.
Comment 1 Aryeh Gregor 2011-09-15 21:28:45 UTC 
IE10PP2: Returns gibberish (16777215)
Firefox 8.0a2: transparent
Chrome 15 dev: rgba(0, 0, 0, 0)
Opera 11.50: rgb(255, 255, 255)

So it looks like I match Opera here, of all things.  I think returning "transparent" as a special case instead of using rgb(a) syntax doesn't make sense, so I'll go with WebKit here.
Comment 2 Aryeh Gregor 2011-09-16 20:51:06 UTC 
https://dvcs.w3.org/hg/editing/rev/846e125a5e07