| Related to Linux |
| Sometimes drop-down or contextual menus appear at the wrong position on the screen. | |
| Upon moving the parent window, it appears that the menu position is not updated. They still appear at the same position. | |
| To reproduce with affected applications, open app, open drop-down menu, move app window, open same drowpdown menu - observe that the menu has not moved with the window and is subsequently now appearing at a wrong position. | |
| If the window is resized, the menus get re-aligned. | |
| Weston 3.0.0 | |
| (running in DRM mode) | |
| There is such a bug in sway too. But over there it seems to affect everything (pcmanfm, lxterminal, subl, chromium...) |
... to place markers on a map.
This code runs in the browser debugging console.
I parse this page to extract geographical coordibates for major cities:
https://en.wikipedia.org/w/index.php?title=List_of_cities_by_longitude&printable=yes
Just open this page in your browser, launch your debugging console and get ready to copy-paste.
| <?php | |
| // ============ strings ================ | |
| function smart_truncate($string, $limit, $break=" ", $pad="...") { | |
| // truncates string to the first $break after $limit characters, then adds $pad to the end | |
| // Original PHP code by Chirp Internet: www.chirp.com.au | |
| // Please acknowledge use of this code by including this header. | |
| // return with no change if string is shorter than $limit | |
| $string = strip_tags($string); |
| /* | |
| * Tries to detects whether a given string is "Arabic" (or Farsi, Pashto, etc.) | |
| * The detection is based on counting "Arabic alphabet" characters | |
| * Returns true if the string is mostly made of "Arabic characters", false otherwise | |
| * This is how to use on HTML element "el": | |
| * detectArabic(el.innerText) | |
| */ | |
| function detectArabic(string) { | |
| try { |
| // override XMLHttpRequest | |
| // source: https://gist.github.com/icodejs/3183154 | |
| var open = window.XMLHttpRequest.prototype.open, | |
| send = window.XMLHttpRequest.prototype.send; | |
| function openReplacement(method, url, async, user, password) { | |
| return open.apply(this, arguments); | |
| } |
| - Side effects (usually unwanted) | |
| - Sometimes impractical: eg: vertical-align | |
| - Sometimes too high level / opinionated and inflexible (related to all of above) | |
| - Cascading - most of the inhertiance is unwanted | |
| - Global-variable-like issues | |
| - Overriding | |
| __Improvements | |
| I think it would be an important improvement, to be able to compound CSS blocks. A bit like less mixins, but at a native level. At the moment, if we are not using a pre-processor, we have to add multiple classes on elements (eg: <div class="col-2 pad-1 size-3">). That is neither powerful nor semantic. |
| /** | |
| * Generates html element based on a d-structure | |
| * d-structure is: | |
| * [ string tagname | HtmlElement root_element, | |
| * object attributes, | |
| * [child] | string text, | |
| * funcion callback(el) | |
| * ] | |
| * child is: | |
| * d-structure | string text | HtmlElement element |
| // credit: https://codepen.io/gabrieleromanato/pen/LpLVeQ | |
| function parseInputs( elements ) { | |
| var obj = {}; | |
| for( var i = 0; i < elements.length; ++i ) { | |
| var element = elements[i]; | |
| var name = element.name; | |
| var value = element.value; | |
| if( name ) { |
| /* Source: | |
| http://stackoverflow.com/a/30743013/370786 | |
| */ | |
| /***** Attribute Hacks ******/ | |
| /* IE6 */ | |
| #once { _color: blue } | |
| /* IE6, IE7 */ |