493880 - Merge Core:Content into DOM

Status: RESOLVED FIXED

(bugzilla.mozilla.org :: Administration, task)

Description

[Zack Weinberg (:zwol)]

If you start filing a Core bug and select 'Content' from the components list, the description box says "Component description missing".

I'm not sure what the exact scope of Content is, unfortunately.

Comment 1

[timeless]

It actually uses <blink>:

<blink>Component description missing</blink>

i.e. whenever this was created, someone probably gave us a list (quite possibly to me) and presumably didn't include a description, but creating the component was more important, so a placeholder was provided which was supposed to get someone to think about fixing it.

if i'm right though, this description is probably 9 or so months old, which means it didn't work :(

thanks for filing the bug.

Comment 2

[Jonas Sicking (:sicking) No longer reading bugmail consistently]

I was the one responsible for suggesting this component, and I actually regret
doing so. I think we should just merge it with the DOM component.

Basically the idea was "bugs on stuff in the content/ directory that doesn't
fit in any of the other components". But since the content/ directory is in the
process of dying, and because it's hard for non-content/-developers to know the
exact scope, i think we should just merge it with the DOM component.

Comment 3

[timeless]

ok. i'll kill it

Comment 4

[Zack Weinberg (:zwol)]

as the reporter, let me just say that merging with DOM would be fine by me.

timeless: you don't disable <blink>?

Comment 5

[timeless]

Deleted
Component: 	Content
Component Description: 	Component description missing
Default assignee: 	[e-mail]
Default QA contact: 	[e-mail]
Component of Product: 	Core

Zach: oh, i'm not saying it blinked at me, i'm just saying that the literal html (which people who edit components) can see had a blink. It wasn't blinking at me in the browser I was using when I checked the component description but it was there in the source.

The reason I mentioned it at all is that it's possible for a component to literally not have a description, in which case it shows up in red to warn editors like myself, and this was not the case. i.e. it was clearly intentionally set to that value instead of being accidentally emptied of any value.