Already implemented! [WAS] Suggestion Preview: clearly delineate the preview/remove extra text

[ninetydegrees]

This is already implemented. I had some custom coding which prevented me from seeing the separation. My apologies.

---

Title:
Suggestion Preview: clearly delineate the preview/remove extra text

Area:
http://www.dreamwidth.org/site/suggest

Summary:
When you preview your suggestion I find it a bit difficult to spot what's the preview and what's a repeat of the suggestion page. There is no separation between the two.

Description:
Ideally, I'd like all the extra text starting from 'Have a way to make Dreamwidth better?' to be removed from the preview and a simple <hr> line to be added but, if that can't be done, just the line would be useful.

Here's a screenshot to show you what I mean: http://i38.tinypic.com/2j31f6c.jpg

Poll #1536 Suggestion Preview: clearly delineate the preview/remove extra text

This poll is closed.
Open to: Registered Users, detailed results viewable to: All, participants: 3

View Respondents

This suggestion:

View Answers

Should be implemented as-is.
0 (0.0%)

Should be implemented with changes. (please comment)
0 (0.0%)

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
1 (33.3%)

(Other: please comment)
2 (66.7%)

Comments

[yvi]

...

But there's [hr]s in the code. I know because I put them there.

And they show up for me. But your screenshot somehow doesn't have the spellcheck.

I am confused.

http://s241.photobucket.com/albums/ff91/Yviwriting/previewsuggestions.png

[yvi]

denise and I are trying to work this out. Looks like browser-weirdness.

[denise]

....And it works (with spellcheck and hrs) in Firefox for me, but it doesn't preview at all in Safari.

How weird.

[yvi]

http://changelog.dreamwidth.org/419149.html It's not that strange code :( Does safari also have a problem with comment spellchecking?

Edit: With which I mean that I was seriously not expecting this to be affected by what browser is used. I probably should have known better ;)

[denise]

No! Not at all.

[ninetydegrees]

It does! As I said to Yvi, I had some custom coding (but maybe you go that comment with the shiny new track option for maintainers :). My apologies. Should I delete this post?

(BTW, I have a question about a suggestion you rejected (I think we misunderstood each other). Can I ask here or should I PM you?)

[denise]

I have PMs turned off because I hate them, but you can email me!

[ninetydegrees]

Done. Thanks!

[ninetydegrees]

I'm so sorry. I had some custom coding which made it disappear. My sincere apologies. I'll ask Denise if I should delete this.

[denise]

Well, that solved that problem at least, but now we have to figure out why it isn't working in Safari *g*

[yvi]

Well, the syntax is from talklib.pl . Strange, strange.

[afuna]

Oh! I see it now. It's because </form> is closed twice :)

[yvi]

...

Oh. :)

[yvi]

By which I mean that I will put it into Zilla and fix it. I am feelink like small bugs today.

[afuna]

\o/

[yvi]

Heh, no need to apologize :) Looks like we are uncovering some browser-related bug here, at least!

[sophie]

What was the custom coding, out of interest?

[ninetydegrees]

Something simple: I dislike HR lines on site-schemed entry pages so I set them to display: none.

And if I misunderstood your question: I have custom coding for the whole site, some of which is already on userstyles.org but the part for #content isn't.