Downplay the "Abuse" button in the new custom desc.

[Cogliostro]

There is a big green button- "report abuse" in the character description, and WAY too much distracting small text with disclaimers and guidelines all around it.

The main problem I'd like to address is that the green button. A button of that kind should really be reserved for Cantr gameplay functions only. It just looks like a gameplay (in character action) button, and that's very confusing. Let's move the button from this screen to the one that appears when you click on the "Guidelines" smalllink text.

Beyond this, (as step two) let's also get rid of the small print disclaimers on this page (moving them to Guidelines too), so that this page can be dedicated to what it's for, seeing at a glance the clothes/weapons and player description of the character.

[AlchemicRaker]

Agreed. The description is good, being placed at the top, but the two acres of other... extras... and that green button... need work. Like, relocation work.

- Natso

[Doug R.]

I greatly disagree. I can see converting the button to a link and moving it NEXT to the guidelines link in the small disclaimer, but I feel the link and the disclaimer needs to remain. Two acres? It's two sentences in a smaller font. I barely even notice it. If the two acres comment was directed at the paragraph above your own description box, then yes, I suppose it could be trimmed a bit, but as it's not part of the view character page, I don't see what the big deal is.

[SekoETC]

As far as I can remember, I placed the button inside the <small> tag along with the text to make it smaller, but I'm not sure if it works that way with buttons.

[Rebma]

What doug said about it being changed to a link might be better. I agree that the button is large and slightly out of place looking. But in all reality it doesn't affect me at all whether or not it's there. Moving all that elsewhere would actually make it a bit difficult for anyone looking to report something. Lets put it this way, I like that you can actually find the button.

[KVZ]

Button as button should stay. I not see problem with its colours.

[SekoETC]

I enabled people to see their own descriptions and at the same time moved the report button to the end of the block that explains what it is. I agree it would be better if it was smaller, and I tried to create a new class in the css file for a small button but for some reason even changing font style from bold to normal causes the whole thing to disregard all custom modifications so I don't know how it works. It's as if it didn't detect the existence of the class, although I don't know how I could define it wrong when I just copypasted another entry and changed the name.

[Rebma]

I wondered where it ran off to..

[the_antisocial_hermit]

I think it should be a link that looks like the link to the guidelines. The disclaimer doesn't bother me, but I think it'd look a little neater overall if the button were just a link. Though it looks better than it did by being moved. There's just really no place for a "button" in that area because everything else is text or link.

[SekoETC]

I think HTML is just built in such a way that in order to submit data, you're supposed to click a button. You can sort of go around it by using a graphic or adding get data to the url but the latter is limited to 100 characters and descriptions are far longer than that. Maybe the meaning of a button is to inform the user that information will be sent. If there was a link, it couldn't contain a copy of the description, only the id of the offending character, which could be used to fetch the description from the database on the next page, but there's a slight chance the person may have changed the description after you loaded the character description page and before you clicked the link, so the description might not be the same it was when you saw it. It could still be checked from the change logs if you complained that it used to be something that goes against the guidelines even though it wasn't so on the moment of reporting, but overall it just seems like a wrong way to do it.

Hmm... I'm just viewing a tutorial on how to make a button smaller with CSS and the sample button looks just like a regular button in my browser, even though I'm using Firefox. It looks nothing like in the picture. I was wondering, could the issue with me trying to add a new style to cantr.css and failing to see it in action be caused by the css file being cached, so that it never actually loaded the changed file?

[AlchemicRaker]

You don't *need* a submit button, thats just the common way to do it.

Instead, use an ancor tag ( <a> ) but don't give it a url. Instead, give it javascript that runs the Submit function for the form. It has the same effect in the end, and you get to use link-like text, instead of a Submit-type input button.

- Natso

[EchoMan]

Seko, CSS-styles may clash sometimes, so when testing you can always use !important in your styles, like:

Code: Select all

form report input[type="submit"] { /* or whatever the xpath is */
  height: 10px !important;
  width: 30px !important;
  font-size: 9pt !important;
}


[SekoETC]

I ran into a lot of Javascript workarounds on google search but it seems wrong to do it like that. If people were supposed to do it, it would be possible without Javascript. Editing the appearance of the button seems like a better idea.

[Cogliostro]

IMHO if it was a smalltext link (the abuse button itself) would be the best way to go. It's pretty standard these days across the web, forums etc.

[AlchemicRaker]

Similar code is used to link the images that are shown on the character list page. Each image submits its own form (and each form leads to a different character page)

- Natso