Jump to content

(Archived) Bug with Tables, table within a table


luckman212

Recommended Posts

  • Level 5
Posted

I can't figure out how to reliably reproduce this bug,

but what happens is sometimes when you CUT text from one table cell and then PASTE it into another, it winds up with a "table within a table" a single 1x1 cell nested inside the rest of the table cell. Winds up looking like this:

kGVsD.png

UPDATE: I finally figured out how to repro this:

1) launch notepad.exe

2) type:

test
one
two
three

(you need the carriage returns)

3) select all

4) copy

5) go to EN

6) new note

7) insert 3x3 table

8 ) position cursor in top-left cell

9) ctrl+shift+v (paste as text)

you will wind up with this mess:

cN6GF.png

Posted

My experience has been that if you select only the text and then paste, you get a basic copy/cut and paste, as shown in image 1.

post-7505-131906072462_thumb.png

If, however, you select the entire cell and copy/cut, then you will paste the entire cell, as shown in image 2.

post-7505-131906072463_thumb.png

you just have to be careful what you select.

Posted

To build on this, I find the rich text editor confusing because, although it can handle complex html pasted into it, I cannot directly recreate these type of notes. Rather than trying to build all of these in, I would encourage the team to consider a button that swaps between the Rich Text view, to the source code view like vBulletin supports. I know how to do the formatting I want in html, so this would provide me an ease way to format my notes exactly the way I want.

  • Level 5
Posted

adding a "developer mode" or "behind the scenes view" so you could get at the code was something I suggested a long time ago but it was shot down-- EN thought it would be too confusing and potentially dangerous for users to be able to modify this code themselves. I still think its a good idea, especially if such a feature was initially hidden from view and needed to be intentionally enabled before it could be used. But I don't want to get too far off topic.

Posted

Wikis allow a simpler form of markup than HTML, human-readable but which can still be very powerful. Advanced wikis allow wiki markup to coexist with HTML or rtf markup.

  • 1 month later...
Posted

@jkatsy Tables being a bit of a weak point for Evernote :-( is this bug fix part of a more general programme of work on Tables support? Perhaps you're constrained from telling us, in which case I'll understand.

Thanks, Martin

  • 3 months later...
  • Level 5
Posted

ok, thanks. I don't know how rapidly goog fixes bugs, but I starred the bug so I guess I'll get notified when it's fixed...........

  • 1 year later...
  • Level 5
Posted

Was that Chromium bug ever looked into or fixed? This bug is really annoying for anyone who uses tables inside EN.

  • 1 month later...
  • Level 5
Posted

For anyone who still cares about this, it appears that at long last (it's been almost 2 years since I reported this bug -- and just about a year-and-a-half since Emerick reported it to the Chromium dev team) that work has begun on a fix!

 

https://code.google.com/p/chromium/issues/detail?id=98228#c7

 

Hopefully the fix won't take nearly as long, and it can be rolled into an upcoming EN point release in the near future.

Posted

Yep, I experience this bug all the time. As for company with  $225 million funding it takes ages here to fix anything :/

  • Level 5
Posted

It's true that Evernote has a reputation for taking glacially long to fix longstanding bugs and add oft-requested features -- but at least in this particular  case it seems that this one is 'out of their hands' -- the bug lies in the underlying Chromium rich text editing component that EN makes use of.. It's probably not within their means or scope to fix bugs in that engine. Let's just hope that once the Chromium component is fixed that EN bakes it in quickly.

Posted

Sure, I understand that this bug lays on Chromium side, but... (I really don't like to play this card, but still it's valid) as a paying customer I shouldn't really care what kind of open source engine they're using, it's not my problem. They had some reasons to choose Chromium in the first place over developing engine on their own (it surely eased the development in the beginning), but if it now stops them from fixing for over 2 years some really simple bugs maybe they should leave Chromium. Or another idea - maybe they should put some kind of bounty on fixing this bug (like some open source projects start to do), or fix it by their devs and submit a patch... There are some possibilities. Not just ignore it.

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...