|
This[^] is one of them. The width of the first image is set to 600, the same as the others, but displays as 720. It looks fine when previewed, so something is changing during submission.
|
|
|
|
|
This image[^]?
In my browser it's displaying at 700 wide (and smaller on small devices) but click it and you get the full 720 wide image in a popup
cheers
Chris Maunder
|
|
|
|
|
Yes, it's originally 720 pixels wide, but so are all the other images. They look a bit large in articles, so I scale them down to 600. But the first image insists on being 720 wide.
|
|
|
|
|
|
I don't follow. You tried to fix it, but you don't think it worked? The image is 720 pixels wide, but so are all the others. I set all of them to 600 pixels in the article editor, and all but the first one display at 600.
|
|
|
|
|
I didn't touch the images, so no change
You said "so I scale them down to 600" which I assumed to mean you physically created images that were 600px wide and then uploaded them. I assume you mean you set the width attribute on the IMG tag at 600 to have the browser scale it.
In that case, I'll dig in and see why it's showing at 720.
cheers
Chris Maunder
|
|
|
|
|
I re-scaled the originals, which fixed the problem in this article. I'll do the same to other articles that have the problem. But it's a curious bug and may only occur when the article has more than one image.
|
|
|
|
|
#realJSOP wrote: this seems contrary to the purpose of the Preview functionality that's available while you're editing
You mean when you switch from source mode to WYSIWYG mode, or when you hit the Preview button?
The Preview renders the article exactly as the article display page would. The exception is that once you publish, your images may get moved (eg you move sections or you go from pending (working image directory) to published (published image directory) hence the missing images.
There's also the issue of caching. Sometimes the browser (especially Chrome) is like a dog with a bone and won't let go.
I've re-edited the article (which forces the cache to be cleared our end) and that intro image is where it should be.
cheers
Chris Maunder
|
|
|
|
|
Chris Maunder wrote: The Preview renders the article exactly as the article display page would.
Yeah - what I'm saying is that the article *editor* doesn't match the Preview. That's confusing and frustrating because there's no way to "fix" what's happening in the preview because they're not the same.
I'm using Firefox (I only use chrome for porn - in a Linux VM). 
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
The live WYSIWYG editing component uses the same stylesheets as the article display so should be the same. Subtle differences will come into play if our system needs to sanitise the HTML. You add script, or layout we don't accept (eg a 10000px wide div or crazy fonts), or you enter broken HTML.
The HTML you enter is auto-formatted by the editor, and then goes through our formatter to clean, to process images, to colourise code, and to ensure it's well formed.
In your case the issues were that their was malformed HTML and "incorrect" image paths (they seemed good, but hardcoding paths means they were fragile). The other thing that got you was using clear:both. The "clear" CSS is notorious and so CSS frameworks add their own clearfix class that actually does the job as one would expect. Things like that can certainly make things a little weird.
There's another subtlety that may come into play: when you switch back and forth from Source mode the editor will go through and make the HTML well-formed. I don't recall if it take your HTML, makes it well formed, then passes it to the editable DOM element, or if it formats it the other direction, or both. If it only corrects it one direction then you may miss seeing a change that's been made. Not sure on that one but we use CKEditor which has proven to be pretty solid and sensible, so I'm guessing this is probably not an issue (just hypothesizing here)
cheers
Chris Maunder
|
|
|
|
|
I am unable to publish article due to error of "Please choose a section for the article".
While first time drafting article, it was selected but after clicking publish button, error raised and further not able to select section due to no list in dropdown box.
|
|
|
|
|
Which article? I saw there was an article in draft form under your account but it was empty (and no auto-saved drafts so I assume it was never worked on)
cheers
Chris Maunder
|
|
|
|
|
I have saved this draft but after error it is showing empty.
This was happened 3 times.
Mahesh Patel
|
|
|
|
|
While tidying up D&A - the random keyboard masher's forum of choice - I found something new (or at least, new to me). CTRL + the "Delete message" button opens the confirmation in a new window - so with a bunch of 'em, hold CTRL down, click each button, then use CTRL+TAB to confirm each of 'em without having to move the mouse about so much.
That's brilliant - saves a little time when batch deleting "Message Closed" messages.
A little tiny change would help though: if the CTRL key is held down when confirming the delete, the newly cleansed page is opened in a new tab as well. If it could remain in the current tab, it would be one less operation: CTRL+click "delete" on six closed messages, then CTRL+TAB to visit each confirmation box, and don't move the mouse off the confirm button, just click it, and press CTRL+F4.
At present, I have to remember to release CTRL before I click and then hit it again for the "close this tab" command, or I get a new tab opening with the rest of the closed messages in it and have to CTRL+TAB past it.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
I've been puzzling over this one.
First: this may sound dumb but D&A? Not sure what that is
Second: it sounds like this is actually a browser thing.
Let me know which page your own and I can see if I can think through something to make life easier.
cheers
Chris Maunder
|
|
|
|
|
Chris Maunder wrote: First: this may sound dumb but D&A? Not sure what that is
That might have been fat fingers trying to type S&A (Spam and Abuse forum)
  
But it actually is the "Design and Architecture" forum, the favourite target of the "Mr. Keyboard" (random keystrokes trolls).
M.D.V. 
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
As Nelek said: Design and Architecture Discussion Boards[^]
Last couple of weeks we've been getting a load of the same stuff in there - a dozen or so random keystrokes as a message.
Probably, it's a spambot in training but it leaves a fair amount of detritus around in the form of "Message Closed" filling half a page. It'd just be nice to reduce the RSI when deleting 'em! 
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Gotcha
What you're seeing is standard browser keystroke handling. I'd love to take credit, but I'd be lying.
As an aside: it being slightly difficult to delete is actually by design. We had issues many, many moons ago where people got a little trigger happy.
cheers
Chris Maunder
|
|
|
|
|
Damn!
How about ... enabling the ENTER key to delete? CTRL+ENTER isn't browser behaviour (except in the address bar, where it adds ".com" and goes to the address).
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
All questions in Q&A are "aging" as "1 second" old or updated.
It was only in wine that he laid down no limit for himself, but he did not allow himself to be confused by it.
― Confucian Analects: Rules of Confucius about his food
|
|
|
|
|
There's something wrong with link to OriginalGriff's tip: Transferring information between two forms, Part 2: Child to Parent
Check the link: Transferring information between two forms, Part 2: Child to Parent
When you click on it, you'll be "transferred" to 404 Spoon not Found site:
Quote: Do not try and find the page. That’s impossible. Instead only try to realise the truth
I'm using it quite often while answering QA questions. Can you fix it?
BTW: other tips about transferring data between forms are OK.
|
|
|
|
|
Hmmm. It seems to work for me. Could you please try clearing your cache and trying again?
Thanks,
Sean Ewington
CodeProject
|
|
|
|
|
This was very strange. I tried to open OG's tip on Firefox and MS Edge. Both with the same result...
I tried to use CTRL+F5, but it didn't help in FireFox. So, finally i followed by this instruction: How to clear the Firefox cache | Firefox Help
|
|
|
|
|
In my experience, Ctl-F5 doesn't clear the cache. It's more an instruction to reload the page from the source and ignore the cache.
It doesn't always work - perhaps related to complexity in the back-end so you're reload may be correctly executed but the data request goes to where it was, before, as that's still cache related. Now you know how to really clear the cache.
Something else, as a hint, that I've found useful: and an argument to the URL, like ?xyz=123 or &xyz=123 if there are other arguments. This informs the browser that it needs to look for updated data (or so it thinks).
It can be stubborn. Where I work, with virtually everything web-base. My stuff all include a do-not-cache directive in every header.
| Ravings en masse^ |
|---|
| "The difference between genius and stupidity is that genius has its limits." - Albert Einstein | | "If you are searching for perfection in others, then you seek disappointment. If you seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
