Please don't let particular my problem change your attitude about Safari. I am trying to see if it's my web coding. Currently the text on that page is placed there with PUT statements and livecode server. I was using <br> for returns and <br><br> for a new paragraph, which is bad form, but easier to code with the method I was using. And if I write the html normally (with <br> for returns) in the page without using LC server puts, it can be copied properly.
Even if the HTML is malformed, I should be able to copy what I see WYSIWYG text wise... I still like Safari and Webkit, I really don't like Chrome or Firefox, and most Apple users will continue to use it no matter what. I'm still tracing it down some more before making a bug report. I'm making a test page. On Mon, Sep 23, 2013 at 6:03 PM, Mark Wieder <mwie...@ahsoftware.net> wrote: > Jerry- > > Monday, September 23, 2013, 5:48:38 PM, you wrote: > > > Geez, I'm about to stop using Safari. Running Firefox only when > > something doesn't work in Safari is getting old. I think I'll just > > recommend that people I support start using Firefox by default. > > ...and Firefox is such a memory hog that I'm starting to use Chrome > more. I prefer Mozilla to Google, but they've taken the bloated path. > > -- > -Mark Wieder > mwie...@ahsoftware.net > > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode > -- Stephen Barncard San Francisco Ca. USA more about sqb <http://www.google.com/profiles/sbarncar> _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
