|The Post Editor is Ridiculous and Needs Attention...||Shawn von Beast||3/15/12 6:42 AM|
I've seen an entire blog post wrapped between <b></b> tags.
- After making a word bold, the person(whomever) must have tried to get the text to the normal font-weight, and instead the editor closed the <b> right after the word that needed to be bold, the editor decided to use <span class="Apple..." style="font-weight:normal...">s for everything(even images and the dreaded <br>s) and closed the <b> after everything else in the post.
I've seen <br>s wrapped within <div>s every time you press return. Wait! I've seen every new line of a blog post wrapped within <div>s. Why don't you use <p> elements for paragraphs?...come on. Why do you delete <p></p>s when I switch modes in the editor. That, is ridiculous, for I do not comprehend.
Instead of inserting inline styles for everything, please use CSS classes. Look at how simple this is:
Aligning an image: <img src="#" class="float-left" alt="meh" height="xxx" width="xxx"/>
...and until it is decent, I'm sticking to the HTML side.
|Re: The Post Editor is Ridiculous and Needs Attention...||Slumberland||3/15/12 2:37 PM|
|Re: The Post Editor is Ridiculous and Needs Attention...||Slumberland||3/15/12 3:49 PM|
Hmmm. I am not cut out for un-editable posts.
It seems several of the problems are with IE. To hone in on the problems, I'm being strict and refusing to use Internet Explorer, and it appears the following can be stricken from my list:
1) Regular HTML symbols and tags can be typed an recognized in the compose view. Switching over to "html" and back converts them correctly. I can copy and paste. Thank god.
2) When working this way, the "bad html" warnings appear and disappear in real time. No more getting a drink or taking a walk, to wait and see if it liked my HTML.
These are, together, a huge part of my frustration. I am glad they are either fixed, or were never problems. If the latter, please accept my apologies. And worried frown about the inability to edit posts.
Of course, once I have to wade into the HTML view, all bets are off. Text-Align Arbitrary! Apple-span! Kumquat-map!
|Re: The Post Editor is Ridiculous and Needs Attention...||beatmushroom||5/29/12 3:20 AM|
Yeah it really needs attention.
Will turn into this:
Notice how it removes the onclick method. So they wont work if I change views.
|Re: The Post Editor is Ridiculous and Needs Attention...||Shawn von Beast||5/29/12 9:23 AM|
I am forced to stick to the HTML side :( or use CKEditor :)
I hope Blogger adds a new HTML5 WYSIWYG like CKEditor, but keep the clean design.
|Re: The Post Editor is Ridiculous and Needs Attention...||Slumberland||5/29/12 12:54 PM|
Continued experience (grwahahaha nobody cares)
3) I think I understand the <div> madness. They encapsulate each tag so I can move things around. In theory I can rearrange images by dragging them. Text flow and alignment adjust automatically, with the help of the image toolbar.
But it doesn't work. The tags get jumbled immediately. The results are confusing and can appear much later. Suddenly alignment won't work and there are a dozen </div>s at the end.
4) Layout is not a mystery.
5) I think there is some misunderstanding about technical subjects. There exist fields where rules have been codified in an extremely efficient and flexible way, so that a person who wishes to learn that subject can, wielding this small palette, unambiguously define any series of choices.
d) NO. Stop and think about that one. Say I want to make a simple diagram using text characters. Say, an arrangement of cards for a bridge column. Type some addition and subtraction of fractions, grade-school size
These are things which can be done with the greatest of ease on a Typewriter.
WHAT'S THE PLAN, GUYS?
Something should give. Personally, I like Shawn's idea.
In short, this month's grip is that without alignment, layout tools are pretend.
|Re: The Post Editor is Ridiculous and Needs Attention...||comingfrom||8/9/12 12:27 AM|
I'm a forum poster from way back, and have learned to live with this.
They're all trying to be too fancy, and drop in far more tags than necessary, for discussion posts and blogs.
I have come to hate the 'div' and 'span' tags, and have no use for them whatsoever in my posts.
Sometimes, the HTML has so much tags, and gets so screwed up, I have to use the search feature to find and delete every 'div' and '/div' tag, and then every 'span' and '/span' tag, before my post will look like it should again.
One trick I do, is paste any content into notepad, and select and copy it again, before I paste it into my post, so it doesn't paste in the HTML code with it, which then carries on into my typing, due to being with the divs or spans.
If anyone knows how to configure Chrome, so it doesn't drop in all these unwanted tags that create such a nuisance for so many of us, I'd very much appreciate it.
And thank you all, for showing me I am not alone with this issue.
|Re: The Post Editor is Ridiculous and Needs Attention...||Shawn von Beast||8/9/12 12:42 AM|
I fail to understand how you see Chrome as the buggiest browser when, clearly, it's the best of the 3 mentioned. It isn't the browser that's inserting all those blasted <div/>s and <span>s; it's Blogger's post editor that's doing that.
A better way than using Notepad is using CKEditor. That thing is beast! Click to see a live demo. If you click on "Create Post", it will publish but won't show you a message saying it was published, so if you click it twice or more, you'll have that many duplicate posts.