Thank you very much for your time, I'm sure it is extremely valuable. I would not continue with this issue purely for myself, I am also thinking of people who have vision impairments and require a good text browser in conjunction with a reader program. Did you try it in run level 3 or were you in X (run level 5)? Just to be clear, I don't mean to sound angry or condescending at all, please. In X it does not misbehave NEARLY as much as in console mode. Also, did you notice my comment about running it in console mode? You didn't mention whether you ran it in X or in console (multi-user) mode. After I start it then I open the options dialogue and enable javascript to continue. Otherwise it refuses to start and spits out the error message I posted earlier. As I have said I have to disable it manually like that before elinks will start.
Can we make sure we're on the same page here on a couple of things? About the nf file, I know javascript was disabled there.
SUBMITTING FORM ELINKS COMMAND LINE WINDOWS
# Whether to disallow scripts to open new windows or tabs.Ī publicly available web site you can test it with. # Whether to ignore content enclosed by the tag when ECMAScript is # not black, it will break the behaviour of transparency. Note, that obviously if the background is # mostly look very impressive, but some sites will appear # 2 is use document colors, including background. # 1 is use document colors if available, except background # Ask for confirmation when submitting a form. # Options for handling of the forms interaction. # Document browsing options (mainly interactivity). # sure that a box confirming success of the operation will pop up. # When you pressed a button in some manager, this option will make # Whether to run those scripts inside of documents. # extracted from the environment dynamically. Set ui.page = "/rbandmb/.elinks/DuckDuckGo.html" # the environment variable WWW_HOME should be used as homepage URI instead. # command line or when requested by the goto-url-home action. # The URI to load either at startup time when no URI was given on the # This is internal option used when displaying a warning about obsolete Come on, aren't we friendly guys after all? # this file, you can change it by altering the config.saving_style # Obviously, if you don't like what ELinks is going to do with # own comments and so on will be kept as-is. # is not written in this file, but in some file included from it, # and missing options will be added at the end of file if option # options through UI, however only option values will be altered # if you wish so this file is edited by ELinks when you save No problems with Firefox using this same javascript installation.
I have js, js-devel and js-debugging packages installed, all version 1.8.5. I'm using 64 bit.I've tried compiling other STABLE versions of elinks to no avail. This is using the elinks package which ships Fedora 16. Protocols), SSL (OpenSSL), MIME (Option system, Mailcap, Mimetypesįiles), LED indicators, Bookmarks, Cookies, ECMAScript (SpiderMonkey),įorm History, Global History, Scripting (Spidermonkey ECMAScript), GotoĮlinks(render_document_frames+0x18e)Įlinks(doc_loading_callback+0x103)Įlinks(file_protocol_handler+0x151)Įlinks(check_bottom_halves+0x46) (Authentication, BitTorrent, File, FTP, HTTP, URI rewrite, User History, Timer, Marks), Cascading Style Sheets, Protocol Standard, IPv6, gzip, bzip2, UTF-8, Periodic Saving, Viewer (Search
The output of 'bt' command entered inside of gdb (which you run as: Uncovered, please keep the core you just got and send the developers If you would like to help to debug the problem you just Version-Release number of selected component (if applicable):ġ.open elinks config file, ~/.elinks/nf and enable ECMA scriptĪctual result: Attempts to start and does not.Įxpected results: Elinks to open to startup file.Īdditional info:Output dialog following crash:ĮLinks crashed. Elinks crashes with javascript (spidermonkey) enabled
0 kommentar(er)
