Quote
hermes
/*to Dorian*/
Small bug report. Sorry for the bad english.
Steadily falling when selecting any of the encodings KOI8
(working with them need to read messages mail server).
The drop will occur on any page is open, but not empty.
Because at first was glad for 75.1, where many encoding
problems have disappeared, but it was not all.
Quote
hermes
Strange, that. Firefox ESR, and Seamonkey allow without falling use KOI8 (-R / U),
as well as older versions of K-MELEON (for example, 1.5.4 and 1.6+ variation).
That is, the encoding Gecko engine seems to be supported...
Quote
hermes
And another interesting glitch seen steady fall (before and
74, 75, 75.1, 76a, 76b) at the opening pages with incorrect
indication of the path to the favicon, the result has long
become a standard еntry lines in user.js:
Quote
hermes
(-) Do not work dialogues obtain links and graphics pages
(there is a black box).
Quote
JohnHell
Not related to K-meleon 76, but as a development addition.
Dorian, consider to add the dom.popup_allowed_events preference to the popup blocker as this macro example:
http://kmeleonbrowser.org/forum/read.php?9,136186,136186#msg-136221
Initially the preference should be defaulted through kmeleon.js (for example) to the most restrictive as popup blocker is enabled by default and this must be restrictive by default too to work the toggler.
Quote
Dorian
Quote
JohnHell
Not related to K-meleon 76, but as a development addition.
Dorian, consider to add the dom.popup_allowed_events preference to the popup blocker as this macro example:
http://kmeleonbrowser.org/forum/read.php?9,136186,136186#msg-136221
Initially the preference should be defaulted through kmeleon.js (for example) to the most restrictive as popup blocker is enabled by default and this must be restrictive by default too to work the toggler.
Why do you want to change the default? Isn't that too restrictive?
Quote
JohnHell
As we have now in project of a macro/extension development, maybe could be as standalone.
## http://lxr.mozilla.org/mozilla/source/content/events/src/nsDOMEvent.cpp #---------------------------------------------------------------------------- # static const char* const sEventNames[] = { # "mousedown", "mouseup", "click", "dblclick", "mouseover", # "mouseout", "mousemove", "contextmenu", "keydown", "keyup", "keypress", # "focus", "blur", "load", "beforeunload", "unload", "abort", "error", # "submit", "reset", "change", "select", "input", "paint" ,"text", # "compositionstart", "compositionend", "popupshowing", "popupshown", # "popuphiding", "popuphidden", "close", "command", "broadcast", "commandupdate", # "dragenter", "dragover", "dragexit", "dragdrop", "draggesture", # "drag", "dragend", "resize", # "scroll", "overflow", "underflow", "overflowchanged", # "DOMSubtreeModified", "DOMNodeInserted", "DOMNodeRemoved", # "DOMNodeRemovedFromDocument", "DOMNodeInsertedIntoDocument", # "DOMAttrModified", "DOMCharacterDataModified", # "DOMActivate", "DOMFocusIn", "DOMFocusOut", # "pageshow", "pagehide", "DOMMouseScroll", "offline", "online", # "copy", "cut", "paste"
Quote
JamesD
Quote
JohnHell
As we have now in project of a macro/extension development, maybe could be as standalone.
How many of the following strings apply or could apply to the entity called '$popups_events="dom.popup_allowed_events";'?
## http://lxr.mozilla.org/mozilla/source/content/events/src/nsDOMEvent.cpp #---------------------------------------------------------------------------- # static const char* const sEventNames[] = { # "mousedown", "mouseup", "click", "dblclick", "mouseover", # "mouseout", "mousemove", "contextmenu", "keydown", "keyup", "keypress", # "focus", "blur", "load", "beforeunload", "unload", "abort", "error", # "submit", "reset", "change", "select", "input", "paint" ,"text", # "compositionstart", "compositionend", "popupshowing", "popupshown", # "popuphiding", "popuphidden", "close", "command", "broadcast", "commandupdate", # "dragenter", "dragover", "dragexit", "dragdrop", "draggesture", # "drag", "dragend", "resize", # "scroll", "overflow", "underflow", "overflowchanged", # "DOMSubtreeModified", "DOMNodeInserted", "DOMNodeRemoved", # "DOMNodeRemovedFromDocument", "DOMNodeInsertedIntoDocument", # "DOMAttrModified", "DOMCharacterDataModified", # "DOMActivate", "DOMFocusIn", "DOMFocusOut", # "pageshow", "pagehide", "DOMMouseScroll", "offline", "online", # "copy", "cut", "paste"
I have an idea for a macro. It would not require any change to Dorian's current code. It would allow both novice and experienced users control over the amount of restrictions to be imposed. It would even have a 'try and decide' feature. I do not see 'touchend' in the list. I may not have the right list.
Quote
siria
Important BUG: iniwrite is still ANSI only
Quote
siria
And am currently playing a lot with UndoLastClosed for a macro.
Can remember session-stuff was mentioned before, but don't remember details, so here a possibly duplicate (?) bug report:
- open browser (=about:home)
- restore a session (opens fine, 1 window with tabs)
- Undo Last Closed => a 2nd window opens for about:home
Quote
siria
Something very weird is going on with restoring scrolling positions... Don't fully understand it, but it seems to be rather stubborn in restoring "old" positions ;-) Seems to happen especially when restoring, scrolling further, closing again, then restoring again, it opens at some "old" scroll position. Also when reloading an open page, the position stays where it is and this seems to reset a new "stubborn" position too.. When scrolling down further, close tab, and restore, the *reloaded* position gets restored...
Quote
Dorian
Ini must be unicode else it writes ansi. That's how the windows api works.
Quote
siria
Quote
Dorian
Ini must be unicode else it writes ansi. That's how the windows api works.
Hmm, if the file exists already and is UTF-8, the macro still writes wrong characters into it. Or is UTF-8 wrong here? The prob is I cannot figure out ANY way to write e.g. cyrillic or chinese text using iniwrite...