Closed Bug 347833 Opened 20 years ago Closed 13 years ago

plugable comment filters

Categories

(Bugzilla :: Creating/Changing Bugs, enhancement)

2.20.1
x86
Windows XP
enhancement
Not set
normal

Tracking

()

RESOLVED WONTFIX

People

(Reporter: timeless, Unassigned)

Details

i was talking to ispiked about crash logs. it turns out that we want "pluggable content filters". the first couple we'd implement would probably take a comment that has a stack trace and convert it into a set of collapsed and expandable areas. one for "everything" and one for the crashed thread. the one for the crashed thread would show the signature and possibly a couple of callers (no arguments, no offsets, just function names, for a couple of frames). rules: 1. it should be possible to ask each content filter if it has any interest in a comment (this should involve giving it a bug object and a comment object). 2. the comment object should have an array of presentations of the comment, each flavor should have a reference to the filter that generated it (the original one should have a reference to the sql retrieval code). the first flavor should be the raw text from the database, the second flavor should be the html encoded presentation. 3. a filter should be willing to answer a request to refilter a given version of the comment. - if a filter decides that it wants to go between the text and html, it can then ask the html filter to reapply its filter to the text it provides. ideally the linkification/talkback/attachment stuff would all eventually move to this model. 4 (bonus points). each product and user should be able to control which filters are active.
You can use hooks to reformat comments. Besides this, your proposal seems very specific and not something we would/should implement. Also, this RFE got no traction in the last 7 years.
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.