Oh, hidden forum CATEGORY. All right. I'll amend my post.
None.
The "/shouts" function is completely broken on the Global Shoutbox. It does not return a message saying "member ____________ shouted _______ times". It also disables your next shout (You can shout but it does not refresh on your screen. You must refresh the shoutbox to see what you shouted.)
When using it in the shoutbox at the bottom of a page, the "/shouts" function displays the shouts for a particular member as intended, but also "erases" your next shout in the manner described above.
None.
Magic box god; Suck it Corbo
You do not have a shoutbox color. it now is an item.
Why are signatures and titles also items? That's just lame imo
You do not have a shoutbox color. it now is an item.
Why are signatures and titles also items? That's just lame imoTHIS.
I uploaded the fixes for Chrome and IE8's problems to Dev. Once Dev uploads the files to the server, Chrome users should be able to use the BBCode console, and IE8 users shouldn't be forced into IE7 rendering mode on the Forum Index. (The problem was a code for the forum images; it had the exact same result as the
max-height/float/overflow bug listed on this page, but a different cause. I'll report this cause to Micro$oft promptly, so that they can ignore me with maximum efficiency.
(I already reported the details of it before, but the fuckers treated it as a tech support request and not a bug report. No, Micro$oft, I won't restart in Safe Mode and reinstall the fucking browser when I already know the problem's with your lack of programming skill and NOT with my installation.)
None.
IE8 users should be able to browse the Forum Index without being forced into Compatibility View; however, I left some debug CSS in by mistake, so forum images will look weird... and very red.
The dialogs from the bbcode console ought to work in Chrome without refreshing now. If they don't, please let me know in this thread (I'm running very low on PM space).
Dev's next update ought to remove the IE8 debug CSS and change the navigation's "..." into triangles.HAHAHA, DISREGARD THAT, FTP WORKS NOW. I'll upload the fixes myself.
None.
[*]Bug: The shoutbox mangles non-ASCII characters.
[Ed. note: the problem is actually a general non-compliance with non-ASCII characters. Several PHP native functions deal exclusively with ASCII; their use might be the cause of the character encoding issues.]
This error looks like using htmlentities or htmlspecialchars without setting the optional $charset argument to 'UTF-8'. If that's the problem then it is a
really easy fix (just add that argument).
If it's not and if it is ever necessary, I'm willing to dig through code to find the problem.
TinyMap2 - Latest in map compression! ( 7/09/14 - New build! )
EUD Action Enabler - Lightweight EUD/EPD support! (ChaosLauncher/MPQDraft support!)
EUDDB -
topic - Help out by adding your EUDs! Or Submit reference files in the References tab!
MapSketch - New image->map generator!
EUDTrig -
topic - Quickly and easily convert offsets to EUDs! (extended players supported)
SC2 Map Texture Mask Importer/Exporter - Edit texture placement in an image editor!
This page has been viewed [img]http://farty1billion.dyndns.org/Clicky.php?img.gif[/img] times!
My FTP access is gone, guys, but I managed to slip in a few extra tweaks while I had it.
- Pressing enter in the LIST modal adds a new list item, instead of adding the list to the post.
- Most modals that expand after being opened (such as the LIST modal) will now remain centered, and they cannot expand to the point where they go off-screen. (Their sizes are constrained and scrollbars appear.)
[I say "most" because there's no way for me to automatically detect, in code, when a modal's size changes. I actually have to manually code in a function call whenever something is done to change the size. If I forget that function call, the modal is neither centered nor constrained.]
Unfortunately, I still have to do all of the below, and then PM it to Devourer. This, when my PM space is running tragically low.
(@Dev: The ability to export PMs as plaintext would be nice. So that a PM that says "
Balls" gets exported as "
[color=#FF0000]Balls[/color]", for example. It'd make it much easier to save PMs to one's hard drive.)
Updated bug list:Bugs listed in
orange are critical. Items listed in
green are quick and/or easy to implement.
Fixes to be uploaded:- Feature: Toggle the fullview modal between a real fullview and shrink the image to fit the modal/window.
- Other stuff that I actually can't even remember. I'll have to go digging through global.js again... I may've fixed the regression where collapsed forums aren't remembered; I don't recall.
Fixes to be coded:- Bug: It is possible to tab outside of a modal dialog, interacting with elements that are supposed to be blocked. This results in several bugs, including the opening of multiple modals at once.
- Bug: If multiple modals are opened at once through a glitch, then closing one modal will remove the lightbox (black fade) effect even though other modals are still open. (The fade should remain as part of a graceful failure, or opening multiple modals should be completely impossible.)
- Bug: The rectangle behind the topics in the topic list should not have onclick JS to link to the page.
- Bug: Clickable area of the SC2 tab is too large.
- Bug: Marking a subforum on the Forum Index as read will not show any visual effect of the fact until the page is refreshed. The JS should be altered to turn the subforum grey when the AJAX completes.
- Feature request: Make it so that when viewing large images on SEN, you can switch between seeing it fullscreen and seeing it full-size.
[Ed. note: I'll take that to mean "add a feature that shrinks the image to fit the window during fullview". I can do this client-side and have it remembered with cookies, but if you want it as a setting, Dev'll need to handle it.]
- Enhancement: Modify the image fullview so that the image itself can be easily opened in a new tab.
[What do we do if the image was enclosed in a URL bbcode tag? I guess we do nothing, and leave the resulting hyperlink unaltered.]
- Bug: In Opera, on the Forum Index, the clipped corners on the right sides of section headers are positioned wrongly.
- Bug: The site's appearance has not been perfected in IE. There are some flaws in IE8, and there are many issues in IE7.
- Bug: The Shoutbox's "Extras" button is yellow and a different height from the "shout/refresh" buttons.
- Regression: Collapsed sections on the Forum Index are no longer saved.
The Forum Index uses new JS for collapsing, since the old collapse JS (still used elsewhere in the site) is just awful. The new code JS doesn't have cookie-related functionality built-in. I just need to add cookie code for remembering collapsed sections.
- Bug: The quicksearch text field does not clear the "search" text on focus.
- Bug: The "quote" button in the BBcode Console does not retain proper capitalization when pressed. (Note that the "B", "I", "U", and "S" buttons did toggle case in v5. They're fine.)
- Bug: Some keyboard shortcuts shown in the mouseover tooltips for message formatting do not actually work. (Alt-Shift-U for underline, Alt-Shift-P for image, etc. do not work).
[Ed. note: These are implemented using an HTML feature, "accesskey". Unfortunately, the first part of an accesskey shortcut varies between browsers, with some using Ctrl+Shift, some using Alt+Shift, etc.. Really, these tooltips should be removed -- unless JS can be written to definitively detect a browser's accesskey implementation.]
- Bug: Alt-Shift-U is listed both as the shortcut for underlining and the shortcut for hyperlinks.
- Bug: The parent for #inlinepopup2 is "solid"... Depending on how you've scrolled, this element, located near the lower-left corner, may cover up text or other elements, acting as an "invisible wall" for the mouse and making covered objects unclickable.
- Enhancement: Clicking the middle mouse button on a fullview modal should scroll the image, not the page behind the modal.
Technical details
It's possible to tab out of a modal. This could possibly be fixed by detecting bubbling focus events anywhere on the BODY, and checking the event target. If the target's outside of the modal, focus the first focusable element in the modal (or its first button).
The code to remove the modal fade should check if multiple modals are opened. Alternatively, the SEN.GUI.Dialogs._Dialog constructor can simply prevent the creation of a second modal.
The size of the SCII tab's clickable area is a result of my (successful :3) quest to achieve near-perfectly-semantic markup in the header. At the time, I figured no one would notice it.
The Opera bug is just that: an Opera bug. I've analyzed it and can prove that it's a browser bug, not bad code. Since there's no way (legitimate or CSS-hack-based) to target CSS specifically for Opera, I cannot fix it without breaking it in every single other browser. I've filed a bug with Opera using their website, providing them with a description of the problem and a link to the affected page (SEN's Forum Index). Hopefully, they'll fix the bug soon, because there's nothing I can do on my end.
The Shoutbox "Extras" button is styled differently because it is "fake": it's an A rather than an INPUT[type=button]. I'll need to write specific CSS for it; no biggie.
For accessibility purposes, the "Search" text in the quicksearch should be changed into a LABEL and shown over the textfield when the textfield is empty. This can be done with CSS and JS, and it can be made to degrade gracefully.
Post has been edited 1 time(s), last time on Aug 10 2010, 3:37 am by DavidJCobb.
None.
Searching the shoutbox for "X shouted by member Y" clears the "Y" field after you navigate to a different page in the search results, making it return all shouts containing keyword X rather than only shouts with X said by Y.
None.
The collapse option for all forums except "Staredit.net Functions" does not work. It was working a few days ago, but I guess you guys changed something around.
Also, I mentioned earlier in the other thread: "Unless it's intended, forums that are collapsed don't stay collapsed after a refresh . "
None.
We are aware of that, lotus
Please report errors in the Staredit.Network forum.
The collapse option for all forums except "Staredit.net Functions" does not work. It was working a few days ago, but I guess you guys changed something around.
Also, I mentioned earlier in the other thread: "Unless it's intended, forums that are collapsed don't stay collapsed after a refresh . "
Not sure if I fixed the "only the first section can collapse" bug, but once Devourer uploads a JS file for me, the Forum Index should remember collapses... and a little surprise oughta be added to the dialog that appears when fullviewing images...
Also, Devourer, I like how the first row of smileys in the BBCode console is randomized, but duplicates appear. I'm seeing
right now.
None.
The collapse option for all forums except "Staredit.net Functions" does not work. It was working a few days ago, but I guess you guys changed something around.
Also, I mentioned earlier in the other thread: "Unless it's intended, forums that are collapsed don't stay collapsed after a refresh . "
Not sure if I fixed the "only the first section can collapse" bug, but once Devourer uploads a JS file for me, the Forum Index should remember collapses... and a little surprise oughta be added to the dialog that appears when fullviewing images...
Also, Devourer, I like how the first row of smileys in the BBCode console is randomized, but duplicates appear. I'm seeing
right now.
It's way more lines of code to check for duplicates than just retrieving four random entries ;o.
Does it matter?
None.
way more lines? Actually just two to three lines more than currently.
Please report errors in the Staredit.Network forum.
way more lines? Actually just two to three lines more than currently.
Well, depends on how much you fit on a line
.
PM char limit now displays "10000" sometimes as intended but I still occasionally get a "NaN" for characters remaining when I use quick reply.
The onclick JS for images also does not function as intended on mobile Safari (doesn't center the user's view on the image modal)Never mind, too minor. I can just zoom in on the images as they are right now, lmao.
None.
The onclick JS for images also does not function as intended on mobile Safari (doesn't center the user's view on the image modal)Never mind, too minor. I can just zoom in on the images as they are right now, lmao.
Mobile Safari's fault for not supporting position:fixed, then.
But, as you said: minor. The page doesn't center your view on the modal, the browser centers the modal on your view.
None.
The onclick JS for images also does not function as intended on mobile Safari (doesn't center the user's view on the image modal)Never mind, too minor. I can just zoom in on the images as they are right now, lmao.
Mobile Safari's fault for not supporting position:fixed, then.
But, as you said: minor. The page doesn't center your view on the modal, the browser centers the modal on your view.
In mobile safari AFAIK the modal was created at the top of the page, and I thought the JS didn't work until I scrolled up.
None.
The onclick JS for images also does not function as intended on mobile Safari (doesn't center the user's view on the image modal)Never mind, too minor. I can just zoom in on the images as they are right now, lmao.
Mobile Safari's fault for not supporting position:fixed, then.
But, as you said: minor. The page doesn't center your view on the modal, the browser centers the modal on your view.
In mobile safari AFAIK the modal was created at the top of the page, and I thought the JS didn't work until I scrolled up.
Exactly, Aristo, that's what I'm saying.
Explanation.
CSS can control the placement of an element.
position: static
This is normal positioning for elements. Setting their coordinates (using "left", "top", "bottom", and/or "right") has no effect.
position: relative
You can shift an element from its normal position by setting coordinates. It will not displace other objects if moved in such a manner; it will overlap them, and usually display over them.
position: absolute
The element is positioned absolutely by its coordinates, and does not affect the placement of other elements. In many cases, it is positioned relative to the document. It will usually display on top of anything it overlaps.
position: fixed
The element is positioned absolutely by its coordinates, and does not affect the placement of other elements. It is always positioned relative to the window, such that it scrolls with the window. It will usually display on top of anything it overlaps.
Mobile Safari is interpreting "position: fixed" as "position: absolute". If I say "position:fixed;left:0;top:0", that puts an object in the top-left corner of the screen. If I say "position:absolute;left:0;top:0", that puts an object in the top-left corner of the page. Mobile Safari, then, is putting the modal at the top of the page instead of the screen, which is what it should be doing.
Also, guys, I'm aware of the "Post #X" link breakage and am working on a fix.
None.
Updated bug list [09/07/10]Bugs listed in
orange are critical. Items listed in
green are quick and/or easy to implement. Posts in
purple are bugs that were reported without sufficient information; I ask people for more information, but I sometimes like to still make a note here so I don't forget to check for replies.
Fixes to be coded:- Bug: It is possible to tab outside of a modal dialog, interacting with elements that are supposed to be blocked. This results in several bugs, including the ability to open multiple modals at once.
- Bug: If multiple modal dialogs are opened at once through a glitch, then closing one modal will remove the lightbox (black fade) effect even though other modals are still open. (The fade should remain as part of a graceful failure, or opening multiple modals should be completely impossible.)
- Bug: The rectangle behind the topics in the topic list should not have onclick JS to link to the page. (All skins except Turtle.)
- Bug: The clickable area of the SC2 tab is too large.
- Enhancement: Modify the image fullview so that the image itself can be easily opened in a new tab.
[What do we do if the image was enclosed in a URL bbcode tag? I guess we do nothing, and leave the resulting hyperlink unaltered.]
- Bug: The site's appearance has not been perfected in IE. There are some flaws in IE8, and there are many issues in IE7.
- Bug: The Shoutbox's "Extras" button is yellow and a different height from the "shout/refresh" buttons.
- Bug: The "quote" button in the BBcode Console does not retain proper capitalization when pressed. (Note that the "B", "I", "U", and "S" buttons did toggle case in v5. They're fine.)
- Bug: Some keyboard shortcuts shown in the mouseover tooltips for message formatting do not actually work. (Alt-Shift-U for underline, Alt-Shift-P for image, etc. do not work).
[Ed. note: These are implemented using an HTML feature, "accesskey". Unfortunately, the first part of an accesskey shortcut varies between browsers, with some using Ctrl+Shift, some using Alt+Shift, etc.. Really, these tooltips should be removed -- unless JS can be written to definitively detect a browser's accesskey implementation.]
- Bug: Alt-Shift-U is listed both as the shortcut for underlining and the shortcut for hyperlinks.
- Enhancement: Clicking the middle mouse button on a fullview modal should scroll the image, not the page behind the modal.
[This might be possible using a cheap, hackish workaround that detects scrolling on the body, undoes the scrolling on the body, and applies it to the modal... Developing such a thing would be... difficult... however.]
- Bug: As of yesterday, using the buttons on the BBCode Console refreshes the page in Google Chrome.
- Feature request: Trash the entire old fullview system and use something like this. It has everything I've been trying to do, could easily be implemented with some mods (support for position:absolute rather than fixed) to the modeless dialog system, and is much more user-friendly -- and without the costs of the current (fit-to-screen modal dialog) solution.
[Requires support for position:absolute draggable dialogs. Requires that draggability be fixed for IE.]
- Enhancement: It should be possible to have a position:absolute modeless dialog. Currently, all dialogs are position:fixed, meaning that they remain "anchored" on screen when a user scrolls. For dialogs like the "Post #" dialog, this can be useless or even annoying.
[This may cause problems with the draggable feature. Code will also have to be written to allow off-screen dialogs to slide into view.]
- Bug: When reporting a post, clicking "Report" on the small dialog that appears does not close the dialog; clicking it multiple times sends duplicate reports.
[This can be fixed by making the dialog use my Dialogs script. It should use the new single-instance enhancement.]
- Bug: When multiple modeless dialogs are on-screen, the depths of the non-sorted dialogs are displayed based on source order. See the collapse box, below.
- Bug: Long words still stretch the Global Shoutbox, as the fix that was written for the Main Shoutbox was never applied to the global one. This needs to be fixed individually for every skin, not just Turtle!
- Bug: The in-field label for the quicksearch is misaligned in IE7.
- Bug: The top and bottom borders are missing from page number links in IE7.
- Bug: Opera only. For draggable modeless dialogs, clicking the "drag" portion does not "focus" the dialog.
[It is possible to have multiple modeless dialogs on the screen, and sometimes, they can end up overlapping. Clicking a dialog brings it to the front, so that if it was being partially covered by another dialog, it is displayed in front. This does not occur if you click the "drag" part of a draggable modeless dialog, however; it remains behind other dialogs even while you drag it.]
Bugs that have been fixed:- Pressing Enter in the LIST modal adds a new list item, instead of inserting the list to the post.
- Most modals that expand after being opened (such as the LIST modal) will now remain centered, and they cannot expand to the point where they go off-screen. (Their sizes are constrained and scrollbars appear.)
[I say "most" because there's no way for me to automatically detect, in code, when a modal's size changes. I actually have to manually code in a function call whenever something is done to change the size. If I forget that function call, the modal is neither centered nor constrained.]
- Bug: Internet Explorer 8 forced users to view the Forum Index in Compatibility View.
- Bug: Forum Images displayed oddly on Google Chrome and Safari.
Bug: Using the buttons on the BBCode Console refreshes the page in Google Chrome and probably Safari.
[Regressed? See to-do list, above.]
- Regression: The Forum Index was unable to remember what sections were collapsed.
- Bug: The Forum Index could only collapse the first section.
- Bug: The Forum Index was unable to remember when a section was uncollapsed.
- Bug: The parent for #inlinepopup2 is "solid"... Depending on how you've scrolled, this element, located near the lower-left corner, could cover up text or other elements, acting as an "invisible wall" for the mouse and making covered objects unclickable.
- Feature request: Make it so that when viewing large images on SEN, you can switch between seeing it fullscreen and seeing it full-size.
- Bug: The "Post #" links were broken for a short time, as they actually used the old fullview code to show modeless dialogs. (I wasn't aware of this, so I didn't update those links when I initially removed the old fullview functionality.)
- Enhancement: It is not particularly easy to make it so that only one instance of a modeless dialog can be opened. This can cause problems. (For example: you can click a "Post #" link several times to spawn several redundant instances of the dialog.) This is required to implement the fullview system suggested by Aristocrat.
[Each Dialog can be given a string to use as a unique name. If another piece of code attempts to create a Dialog with the same name, the already-existing Dialog is returned. The old Dialog is not modified to use the settings specified for the new one.]
- Bug: When the window is resized, all draggable modeless dialogs are forced to the right side of the page; their original positions are not preserved/adjusted.
[Fixed. The problem was that the "update dialog display" function didn't account for draggable dialogs being dragged.]
- Bug: Marking a subforum on the Forum Index as read did not show any visual effect of the fact until the page was refreshed. The JS has been altered to turn the subforum grey when the AJAX completes.
- Bug: In Opera, on the Forum Index, the clipped corners on the right sides of section headers are positioned wrongly.
- Bug: The quicksearch text field does not clear the "Search" text when focused via click, Tab, etc..
- Bug: The entire quicksearch form (save for the in-field label) is misaligned in Opera.
- Bug: Help tooltips will sometimes go off-screen, producing a horizontal scrollbar. Because moving the mouse dismisses the tooltip, it is impossible to scroll and see what's being cut off. This often happened when attempting to see who voted for which options in a poll.
[This refers to the tooltips seen when hovering over graphics..]
- Bug: Dragging is broken in IE7 and IE8 for draggable modeless dialogs.
- Bug: Fixed several CSS issues in IE7. I should note that most of them were IE7's fault, not mine. ><
Technical details on fixes to be coded
It's possible to tab out of a modal. This could possibly be fixed by detecting bubbling focus events anywhere on the BODY, and checking the event target. If the target's outside of the modal, focus the first focusable element in the modal (or its first button). Could be problematic, though, as IIRC focus events actually don't bubble at all.
The code to remove the modal fade should check if multiple modals are opened. Alternatively, the SEN.GUI.Dialogs._Dialog constructor can simply prevent the creation of a second modal.
The size of the SCII tab's clickable area is a result of my (successful :3) quest to achieve near-perfectly-semantic markup in the header. At the time, I figured no one would notice it.
The Opera bug is just that: an Opera bug. I've analyzed it and can prove that it's a browser bug, not bad code. Since there's no way (legitimate or CSS-hack-based) to target CSS specifically for Opera, I cannot fix it without breaking it in every single other browser. I've filed a bug with Opera using their website, providing them with a description of the problem and a link to the affected page (SEN's Forum Index). Hopefully, they'll fix the bug soon, because there's nothing I can do on my end.
The Shoutbox "Extras" button is styled differently because it is "fake": it's an A rather than an INPUT[type=button]. I'll need to write specific CSS for it; no biggie.
For accessibility purposes, the "Search" text in the quicksearch should be changed into a LABEL and shown over the textfield when the textfield is empty and unfocused. This can be done with CSS and JS, and it can be made to degrade gracefully.
For the bug regarding the depths of multiple modeless dialogs... Say you open four draggable modeless dialogs in order, and we'll call them A, B, C, and D.
Drag C so that it overlaps D, and focus C.
Drag B so that it overlaps C, and focus B.
The expected result is that B is in front of C and C is in front of D, but what actually happens is that B and C are in front of B. This is because C and D now have the same (unfocused) z-index and are hence being displayed in source order; D comes later in the code (having been created later), and hence shows over C.
Drag A so that it overlaps B, and focus A.
Now we see the full problem. A is in front of all dialogs. D is in front of C, and C is in front of B. Again: B, C, and D are being displayed in source order.
The only fix that I can think of would be to manually set the z-indices for each modeless dialog, but this is messy and not adjustable with CSS... I wonder if there's another way...
Post has been edited 13 time(s), last time on Sep 8 2010, 6:24 pm by DavidJCobb.
None.
I'm also happy to announce a new website we're developing called
StarEdit TV. SENtv will be a new addition to the StarEdit Network devoted to hosting SC2 tutorials and map previews. The tutorial videos will be linked back to articles on our SC2 wiki, and the previews will be linked to their respective "Production" or "Showcase" topics. SENtv should be unveiled in the next few weeks.
Sorry for the necro, but I wanted to know if SEN.TV was still an under-going project?
I believe it was declared as dead, but seeing the domain is still owned and that GalaxyWiki is taking form, it could be an interesting plus.
And talking of interesting features, for when the implementation of
VGShort? And while we're at it, is it possible to port it into GalaxyEdit as well? And that idea of making hosted maps browsable directly from within the browser?
None.
As far as I know, Devourer stopped all work on SEN.tv. I still own the domain and may do something with it in the future if he doesn't want to try to make it again. I will still do the SEN.tv skin for SEN at some point, when I'm feeling up to it.
Currently Working On: My Overwatch addiction.