• 0

    posted a message on BadApples/Prat Interaction issue?
    I am the maintainer of Badapples; it works very simply by adding a color code around the name of the player. If Prat is stripping that out, there's really nothing I can do about it without expliclitly adding checks and overrides just for Prat, which I don't really want to do.

    Coloring the entire line is an interesting idea, though, and I may consider adding that. I am currently (albeit slowly) rewriting the entire addon, since the original code was written pre-TBC and really shows its age, so any new features wouldn't be added until that's finished.
    Posted in: AddOn HELP!
  • 0

    posted a message on Git Questions
    Quote from Torhal
    This isn't a WordPress site that we can just slap together in a day, however, and the new platform is internally a completely different beast from the old; there are a plethora of subsystems and details to consider, so the process hasn't been as straightforward as you seem to be implying.


    At work, I'm currently on a project with 3 other guys, and in 3 months we've gone from having nothing to having a usable web-based product that's we're not only using in our own business, but also already selling (as SaaS) to other businesses in our industry. Just in the last week alone we've added a new major feature that's roughly as complex as CurseForge's ticket tracker. If you exclude the packager and repositories, I'd estimate the two systems are about equal in total complexity, and you said those were finished ages ago.

    I'd be surprised if my 4-person team could not build a CurseForge clone in under 9 months, and I'd guess closer to 6, especially given that most of the things on CurseForge (ticket tracking, commenting, file listings, etc.) are ubiquitious components with a bazillion existing examples for how they should look and function. And we're not even good at this -- I don't touch the server-side stuff at all and had never worked on this kind of full-stack from-scratch project before, two of the guys had no Python experience and only a little JavaScript experience at the start of the project, nobody is full-time and half the team only works 20 hours a week, we all work around a table in the back room of the retail store owned by the project leader, and a good portion of our time is spent arguing about implementation details or tearing our hair out over conflicted Git merges because our workflow is horrible. Yet stuff gets done, quickly, and there are remarkably few bugs. Obviously it's not as large-scale as CurseForge, but I don't think scaling to more users and more data is what's taking you guys so long.

    On the other hand, Curse has done this -- exactly this -- before, and presumably has full-time employees who aren't learning on the job. It just should not take this long.

    ...Though frankly, considering what I've seen of the beta site, I kind of hope it takes forever because I really don't want to have to use the new site. :(
    Posted in: General Chat
  • 0

    posted a message on Feedback, round 2

    Kaelten asked me to take another look and give new feedback, so here's a new thread since I probably still can't post a reply without using Internet Explorer.

    Summary:

    I don't see a lot of changes. A few things have improved, most things are the same, and some things have even gotten worse. I feel like whoever is writing this stuff is in the same situation as whoever is writing Blizzard's UI Lua code. It's not their area of expertise, but somehow they got stuck with the task and are just kind of muddling through.

    --------------------

    This WYSIWYG editor is still terrible. 13px font size is unacceptable. Controls and even basic input are buggy; for example, pressing Enter sometimes does nothing at all. Selecting text (eg. to apply formatting) is broken and hellishly slow even when it sort of works. The UI is also super ugly and strongly reminiscent of Windows 3.1. Please just get rid of WYSIWYG and implement basic Markdown and/or BBCode support. Anyone posting on a gamer site knows how to use one or both of those.

    I am now switching to Notepad to write the rest of this post.

    --------------------

    On to the actual site! Looking at beta.wowace.com ...

    body { font-size: 13px } is 130000000000000% unacceptable. Stop it. Nobody can read this. If you can, your face is way too close to your monitor and/or you are actually an eagle. I'll be zoomed to 170% for the remainder of testing, which is utterly insane.

    --------------------

    The home page layout seems to have undergone some kind of regression, and apparently wasn't tested in *any* browsers prior to deployment. (Yes, I also checked back at 100% zoom. Problem still exists.)

    - The giant header area's text is off-center in all browsers. This results from specifying "margin-left: auto" on ".home-header div.e-wrapper div.e-container" but not also specifying "margin-right: auto". This is especially bad in IE where it pushes the text all the way to the right. I think it might be intentional that it's not completely centered, but it definitely isn't working as intended in all browsers.

    - The giant header area's background image doesn't cover the full width of the header in some browsers. This results from setting "max-width: initial !important" on "#site .atf" in your CSS. Even though "initial" seems to be allowed in the spec, in practice it seems to not be understood by all browsers. Changing "initial" to "100%" achieves the desired result in all browsers, and is fewer characters anyway.

    --------------------

    You guys should acquaint yourselves with the glory of flexbox and stop floating every. single. thing. everywhere. in your layout.

    --------------------

    You should also acquaint yourselves with mobile-first design. Right now your <body> has a "responsive-enabled" class, and some changes do happen when I resize the window to a phone-like width, but I feel like whoever implemented this stuff doesn't really understand the concept on a fundamental level.

    For example, on the home page, the nonsensical order of things in your HTML source (sidebar content before real content) means that I have to swipe down and down and down and down some more to see the actual page content. You're also hiding some of the page content (the things that tell me what the site is about and what it offers) when it's not really necessary, and you're **not** hiding the incredibly gigantic site header, which is even more miserably gigantic on a phone-sized viewport and also totally useless because the top bar already includes the WowAce logo. I can also see now that you're using a hardcoded linebreak in the header "tag line" which is unnecessary -- just set the width of the element so it wraps in a way you find satisfying -- and makes it look strange at non-desktop resolutions. The "search" icon in the top bar is also broken -- for some reason you've implemented it as a circle icon and a separate bar icon, but they're not arranged correctly to look like a magnifying glass; it ends up looking like a stopwatch.

    --------------------

    Dashboard

    Only shows issues (not comments) and they're not sortable or meaningfully filterable. Filtering by title or description (fake label inside the text field is truncated, and stop doing this, just use a damn label, that's what they're for) is almost never going to be useful (I can't recall a time where I've ever wanted to do this). This list should be filterable by tags (eg. so I can see "all bugs" or "all feature requests") and should be sortable (by submitted date, last commented date, project name, etc.)

    There is also nothing showing me which content is new. Which tickets have I not viewed yet? Which comments (on tickets or anything else) have I not read yet?

    --------------------

    Onward to a project page. Using Grid again for testing since that's what I used last time and it uses every project feature (issues, pages, localization, etc.)

    - Header is way too large. At a readable size (170% zoom) the network, site, and page headers take up more than half of the vertical screen space; at 100% zoom they're still taking up well over 1/3 of the viewport height. You're wasting a lot of horizontal space. Move the site menu (Home, Projects, Forums, Dashboard) and site search box up onto the same row with the WowAce title. In the next section down, get rid of the tiny screenshot thumbnail; it's too small to be of any use. Also increase the size of the project name (it doesn't stand out enough as-is) and remove the "Addons" label (what is that even for?). Now that row is smaller too.

    - The "table of contents" link at the top of the project description is still useless. Again, if you can't generate a meaningful TOC with the chosen markup type (though you really should be able to generate a TOC with Markdown!) don't show this TOC link and its equally useless popup.

    - The first sidebar box ("about this project") is largely non-interactive and uninteresting. Nobody cares when the project was created. There's no need to show the last release date here when it's shown in the "recent files" box where it's actually associated with something actionable (a download link). The total downloads and license are of very little interest to the vast majority of people who will view this page. Move the "view on curse.com" link up next to the "follow" link. Now what's left of this box can be moved to the bottom of the sidebar, since pretty much every other box is more useful/interesting.

    - The "recent files" box should be at the top of the sidebar, since actually downloading the addon is one of (if not THE) most important actions on this page. For the most part this box is pretty good. My only complaint is that the logic should be improved. Currently it's displaying the "latest" alpha file, which is from 2012 because after that I turned off alpha packaging. Beta and alpha files should only be shown here if they're newer than the latest release file. Alpha should only be shown if it's newer than the latest beta too.

    - The "categories" box needs a visual overhaul. Just show the category names as text. These icons are largely meaningless (the only useful ones are for classes and professions) especially at these sizes. Just show the damn category names.

    - The "members" box still doesn't show user avatars, even though it has space for them. It's also not sorted logically. Maia (whose role is "former author") is shown above Pastamancer (whose role is "author"). It should go project owner > author > maintainer > translator (if that still exists) > documenter (if that still exists) > former author.

    --------------------

    Project Page > Files

    For the most part, this page is pretty good.

    However, the way nolib packages are shown is bad. Having a "+1 more" button next to each file is confusing and not even remotely suggestive of its actual meaning (which is that a nolib version of this file is available). Better solutions include:

    - Just show the nolib package below the regular package for each version, like the current site does.

    - Have a toggle at the top (next to the "game version" dropdown) for switching the list between regular and nolib packages.

    --------------------

    Project Page > Files > invidual file

    This page is also bad. The changelog is THE most important information on this page, yet it's almost pushed totally out of the viewport at 100% zoom (and it's definitely out of viewport at readable zoom levels) and shown in a tiny box that requires even more scrolling.

    - Move all the metadata (nobody cares about the filename, uploader name, or MD5 hash; almost nobody cares about the file size; and the download count is only mildly interesting to a few people) from the top of the page into a sidebar. Show the supported game versions first, since that's the only metadata item that really matters to most of the people who will view this page.

    - Remove the scrollbar on the changelog.

    - Move the "additional files" and "related projects" sections into the sidebar below the metadata.

    --------------------

    Project Page > Images

    There's still no way to zoom in and see images at full size.

    Images that have a higher height/width ratio than the thumbnail box are still cropped, with no way to see the hidden portions.

    There's still no way to choose the project's default image.

    There's still no way to change the order in which images are displayed.

    --------------------

    Project Page > Issues

    This page still uses a space-wasting layout and is not sortable.

    If "ticket type" and "ticket status" are going to be merged into a generic "tags" feature, then the tags should be editable. The terms "defect" and "enhancement" are pretty awful, and not intutive to many users, especially users whose native language is not English. "Defect" should be "bug" or "problem", and "enhancement" should be "feature request" or "suggestion" or "idea".

    --------------------

    Project Page > Issues > individual issue

    The contrast on buttons is still way too low.

    There's still a sidebar offering to filter on ticket status and tags, which makes no sense since I'm looking at one ticket, not a list of tickets.

    As with pretty much every other page, there's way too many levels of navigation and metadata bars above the actual content.

    Attached images were not migrated with tickets. Example: http://beta.wowace.com/projects/grid/issues/53666 vs http://www.wowace.com/addons/grid/tickets/806-enable-a-groupnumber-icon-indicator/

    The reply form area seems unfinished, especially the assignee dropdown, tagging interface, and "close issue" checkbox. The assignee and tagging should probably be in the sidebar anyway.

    --------------------

    Project Page > Pages

    As with the project overview, the TOC popup does not show a meaningful TOC outline.

    Clicking links in the page content sends you to an annoying interstitial "are you sure you want to click this link?" page. Nobody likes these, and they don't improve security, especially when they don't even show you the URL of the link you clicked on.Just get rid of it, and do it now. It's also pretty bad when you add them for links to other parts of your own site, like the forums.

    The particular content on this page -- http://beta.wowace.com/projects/grid/pages/faq-and-known-issues -- shows that there's not a good size difference between h1, h2, and h3. They're pretty much all the same size, which defeats the purpose of using heading tags instead of just "big" and "b" tags to mark up headings.

    --------------------

    Project Page > Localization

    Still just as bad as the last time I looked at it.

    There are now slightly more translations per page, but still not enough. If loading translations from your database is too expensive and your server is getting hammered loading 25+ translations per page, add a robots.txt directive excluding these pages from search engine indexing.

    Translations are still not editable on the page. The "edit" link now opens a modal popup instead of loading a new page, but that's not really an improvement. Just make the text an input element on this page like it is on the existing site. Translating is already enough work. You don't need to make it harder with all these extra clicks and popups.

    The search filters should be collapsed by default, with a button to click on them on the right at the same level with the section header (eg. "All Namespaces / English ..... [Filters]"). Also, the filters themselves are unnecessarily difficult to use. Text filters should default to "contains", not "equals" -- or just get rid of that dropdown and always treat it as "contains". There's no need for a "translator" filter here. If I want to see all translations by a particular person, I'll click on their name in the translator list.

    The page numbers at the top are overlapping the box for the first listed translation.

    The namespace title is still given way too much prominence. There's also no need to show the name of the person who created the phrase, or the date the phrase was created. Remove those, move the namespace title to where the username is now, and move the edit/lock/delete buttons and checkbox down onto the same row after "revisions" so you only have one row of things.

    The base phrase is just truncated when it's too long. It's also not shown at all in the translation popup. Both of these make translation unnecessarily difficult. Example: http://beta.wowace.com/projects/grid/localization/languages/43/namespaces/2521/phrases

    A translator would need to mouse over the truncated phrase, read the tooltip, then remember the entire phrase (remember, this person is probably not a native English speaker, and may have limited English fluency) before clicking the "edit" link and the entire time they're entering their translation. This just isn't realistic. I generally do my own Spanish translations, and though my Spanish is decent **and** it's my own addon using text I picked in the first place, there's no way I'd remember the entire phrase in the above case if I had to stop in the middle to go look up one word I wasn't sure about.

    --------------------

    Project Page > Localization > individual phrase

    This page is surprisingly good. My only immediate complaint is that the translations appear to be displayed in a random order. Please alphabetize by locale code, like in the "languages" box in the sidebar.

    I'd also suggest adding a way to view the translation history from this page. Actually, it doesn't even need to be linked from the main list of translations. It's such an infrequent activity that it's better off being relegated to the individual translation page anyway.

    --------------------

    Project Page > Localization > Import Localizations

    Dear god, why?! The version of this page on the current site is 100 times better than this. Two very obvious ways to improve this page and stop making me scroll 4903842342 times everywhere:

    - Move the settings into the sidebar. This page doesn't need the sidebar from the main translations listing.

    - Use a horizontal layout for the settings.

    Also, why are the "missing phrase handling" options implemented as radio buttons, when the other options are all implemented as dropdowns, even those with fewer options? Just make it a dropdown for consistency.

    --------------------

    Project Page > Relations

    Still listing old dependencies that haven't been used in the project since WotLK or earlier. Also would be better implemented as a table instead of a list. There's no need for tiny screenshot thumbnails, download counts, descriptions, or meaningless category icons on this page. A nice simple table like this would be better:

    Title | Category | Author | Updated
    Ace3 | Libraries | Kaelten | Feb 24, 2015
    AceGUI-3.0-SharedMediaWidgets | Libraries | yssaril | Oct 14, 2014
    ...

    --------------------

    Project Page > Settings

    General: List of secondary categories is apparently unstyled. Use something like "column-count: 3" and "column-gap: 20px" to reflow it into multiple columns instead of filling 4 screens with mostly empty space.

    Description: Why is this in the "settings" section? This isn't a project setting, and there's already a dedicated tab for this.

    Issues: Okay, I see I can add and remove tags here. This should probably be moved into the "issues" section instead.

    Issues: When adding a new tag, it's forcibly lowercased. This is inconsistent with the default tags, which all have an initial capital. I'm okay with lowercasing tags, but please lowercase the default ones too.

    Issues: After deleting a tag, if I try to add a new tag with the same name as the deleted one, I get a popup error that says "Unable to Create Tag / An Error has occurred. Please contact support and try again later".

    License: It seems the existing license was not ported over from the current site. That may be related to using a custom license, but it's not really acceptable. In Grid's case it's not that bad, but for someone who explicitly wants their project to be open source, changing it to "all rights reserved" would be pretty bad.

    Client Exclusions: Stop using fake "labels" inside the text field. In this case, the "label" is too long and I can't even see all of it, so I really have no idea what this field is for. Just show the text above the damn field.

     

     

    Posted in: WoW Sites Feedback
  • 0

    posted a message on Git Questions
    Quote from Torhal
    I did say that not following the instructions could cause exactly this problem.


    Right, but the instructions don't work as written, so there's simply no way to follow them exactly. I posted about this and your reply was "well, some other guy wrote that years ago, so who knows", so I did my best with the methods I could find that actually worked.

    Quote from StormFX
    2. Don't push tags along with your commit pushes. Instead, push only the tags you want packaged, separately. That way, you can keep your old tags locally, if only for the sake of history. You could also just leave them un-pushed until the new packager is brought online.


    This sounds miserable, as no GUI client for Git I've ever seen has this functionality -- they all just "push tags". If I wanted to type crap on the command line all the time, I'd use Linux. My first several computers ran DOS, and I don't see why anyone would voluntarily go back to that for basic everyday functionality. :p

    Quote from StormFX
    As far as the actual conversion process, I'm using Ruby and SVN2GIT. It makes it so much easier, as it clones the repo and converts the tags/branches to their git equivalents in one fell swoop.


    Yes, that's what I did, but I had to do some extra work to glue the pre-Curse and post-Curse parts of the SVN history together. I suspect that may be what made the packager die, but it just shouldn't be that hard. I just re-discovered jlam's packaging script, so as soon as I can get that to work on Windows, I will probably just turn off the Curse packager entirely. Despite hearing "it's being worked on!" for years, it's still broken just as often as not. If you guys are that strapped for cash to pay for developer time, just stop giving out so many author reward points... I'd rather have a system that Just Works and get less free Amazon gift cards, than one that makes me want to strangle someone every time I have to interact with it.
    Posted in: General Chat
  • 0

    posted a message on Updating MyAddon.db.char table to point to another table isn't saved accross sessions
    Quote from Nasias
    Say I had a table in self.db.char that had 4 values inside it. The addon would look at the size of this table, and randomly pick a value from it to use. As the user is able to configure most of the settings of the addon, if they only wanted 2 possible values, they would only enter 2 of their own values, and remove the rest.


    If your defaults table looks like this:
    t = {
        "alpha",
        "beta",
        "gamma",
        "delta",
    }

    AceDB doesn't see "table with 4 values", it sees "table with these key/value pairs:"
    t = {
        [1] = "alpha",
        [2] = "beta",
        [3] = "gamma",
        [4] = "delta",
    }

    Remember, Lua doesn't really have arrays, just some special methods for working with tables whose keys are sequential 1-based integers. AceDB doesn't use any of that; it just looks at the plain key/value pairs. Let's say you use table.remove to remove "beta" and "gamma" so your table now looks like this:
    t = {
        "alpha",
        "delta",
    }

    Again, what AceDB sees (since it's only looking at pairs, not ipairs or any other index-based stuff) is this:
    t = {
        [1] = "alpha", -- same as the value in the default table, leave it alone
        [2] = "delta", -- different value than in the default table, but still leave it alone
        [3] = nil, -- no value here, fill in with the default[3] which is "gamma"
        [4] = nil, -- no value here, fill in with the default[4] which is "delta"
    }

    Based on your description, your defaults should specify an empty table, and then after you've initialized with AceDB, check if that table is empty, and populate some "default" values:
    if #t == 0 then
        t[1] = "alpha"
        t[2] = "beta"
        t[3] = "gamma"
        t[4] = "delta"
    end

    Now it won't matter if you remove some of those "default" values, because as far as AceDB is concerned, there are no default values.
    Posted in: AddOn HELP!
  • 0

    posted a message on LuaTexts Official Thread
    Quote from transitbus
    Added check for mapID of your garrison so it doesn't trigger when in your garrison.

    local _, _, difficulty, difficultyName, _, _, _, mapID = GetInstanceInfo();
    if difficulty > 0 and mapID ~= 1159 then
    return difficultyName
    end


    Garrisons have different map IDs depending on faction and level. Instead of checking the map ID, you can just use the C_Garrison.IsOnGarrisonMap() function:

    local _, _, difficultyID, difficultyName = GetInstanceInfo()
    if difficultyID > 0 and not C_Garrison.IsOnGarrisonMap() then
        return difficultyName
    end
    Posted in: Unit Frames
  • 0

    posted a message on Grid — compact party/raid unit frames
    Yep, I've reported it again, but the entire Curse platform is on "no development of any kind, not even critical bugfixing" status while they're devoting all their efforts to developing a new even more annoying platform... despite the fact that they've been working on it for 2+ years and there are some REALLY obnoxious bugs that would REALLY be nice if they would fix. :mad:
    Posted in: Grid & Grid2
  • 0

    posted a message on Git Questions
    The packager is STILL causing problems. Curse.com is currently offering a WotLK version of Grid as the "latest version" and the Files tab on the Wowace.com project page seems to indcate that the packager is re-creating ZIPs for every tag AGAIN.

    Is there any way to fix this other than to delete all tags and overwrite the entire repository? This is ridiculous.
    Posted in: General Chat
  • 0

    posted a message on Git Questions
    Answer: yes, yes it is going to cause problems. Apparently the packager not only recreated ZIPs for every tag, but did so out of order, resulting in some ancient files being the "most recent" on the download page and in the Curse Client.

    I don't have time to go through all the 200-ish files it created and manually click and type through the ridiculous deletion process for every single file. I already reported the project; hopefully file moderators do have a bulk-delete function.

    Really tempted to just hard-embed libs in all my addons so I don't have to use the unmaintained and bug-infested Curse packager anymore... it seems to screw up nearly as often as it does anything right. :mad:
    Posted in: General Chat
  • 0

    posted a message on Grid — compact party/raid unit frames
    Curse is currently experiencing technical difficulties.

    The Curse Client may install an ancient version of Grid, and the downloads list is out of order.

    You can download and install Grid by hand from the following links:


    Do not submit additional tickets or make additional posts about this issue. They will be deleted.
    Posted in: Grid & Grid2
  • 0

    posted a message on Grid — compact party/raid unit frames
    Grid is now in a Git repository instead of SVN.

    The preferred way to submit a patch is to fork the repo on GitHub, make your changes on a branch, and submit a pull request.

    If you're a regular contributor and want direct access to the main repository, give me your GitHub username or email address and I'll add you.

    If you're allergic to Git, you can use SVN on a GitHub repo -- fork on the website, use SVN to checkout, branch, make changes, commit to your branch, and submit a pull request on the website.
    Posted in: Grid & Grid2
  • 0

    posted a message on Grid — compact party/raid unit frames
    Quote from acook24
    Is there an addon that adds focus as a status?


    I'm not aware of any plugins for that. I'm not totally opposed to adding it to the core, since it's small and is a feature of the default UI, but it's not a high priority at the moment. I'd suggest posting a ticket so it stays on my radar.
    Posted in: Grid & Grid2
  • 0

    posted a message on Git Questions
    Okay, after spending several more hours chasing the long tail of Google results and laboriously copying and pasting a series of commands for Every. Single. Tag. to convert them to annotated tags because I couldn't get git-bash for windows to run a shell script, it worked. If I ever convert another old WowAce repo from SVN to Git, the tags do not get to come along.

    That said, I won't be surprised at all if the Curse packager now gets stuck in an infinite loop of trying to repackage every tag 400 times...

    Also all the tags list me as the commit author, but at this point I'm just done trying to make everything perfect.

    Edit:
    It did seem to create new ZIPs for every tag, at least once... is that going to cause a problem?
    Posted in: General Chat
  • 0

    posted a message on Git Questions
    Quote from Torhal
    I've always used http://www.wowace.com/wiki/repositories/convert-svn-to-git/ without issue. I've seen people who don't use that method run into all sorts of issues (such as the packager repeatedly attempting to re-package tags) so that's all I really have to go on.


    That last command, the one that's supposed to annotate the Git tags so CurseForge will accept them, does nothing. I'm using the Git For Windows git-bash. There's no error when I input that command, but nothing happens either.

    Actually, I only tried to use that command after I'd converted Grid's repository using svn2git and Curse wouldn't let me push it, complaining about the lack of annotation on the tags, so that may be contributing to the problem.

    Any thoughts?
    Posted in: General Chat
  • 0

    posted a message on Feedback for beta.wowace.com

    I actually left out a comment about the "report project" button since after reviewing my notes I decided to omit the less critical complaints to focus on the worst ones, but I don't really like how prominent it is now.

     

    Having it front and center is like having "lock your car and hide your valuables" signs in a parking lot -- it makes you feel like you're in an unsafe place where bad behavior is expected rather than an exception, and puts you in a suspicious mindset where you're always wondering "is my car going to get broken into?" or "is this addon really safe to use?".

     

    It was definitely too hard to find on the old site, but I don't like the placement on the new site either.

     

    ----------

     

    Unrelated, this new WYSIWYG control you guys are using is the worst one I can recall using in the last decade. It's incredibly slow and buggy, in every browser. Pasting into the box with Ctrl+V doesn't work in Firefox. Selecting text and clicking the "bold" button may or may not actually apply boldface to the selected text; it seems random, and apparently can be fixed by adding linebreaks on either side of the text, bolding it, then removing the linebreaks. In my first post (above) it seems to have added twice as many linebreaks in between paragraphs as I actually entered in the box. Also in Firefox, I can't type numbers in the box; they're passed back to the browser window as if I didn't have a text box focused -- the only way I can get numbers in here is to type them in the address bar (or Notepad, or somewhere else), copy them, then right-click in the box and click "paste" in the context menu (since again, Ctrl+V is apparently being hijacked and ignored).

     

    Semi-related, while at least the text on these forums is a nice readable black, it's still tiny (14px seriously stop) and many other things also suffer from extremely poor contrast -- see the "upload an image" and other buttons underneath the post input box (the disabled "previous thread" button is literally unreadable) or the horizontal rules in my first post. There also seem to be two different link colors for no reason... some links are blue, some are red, and no, they're definitely not visisted vs unvisited.

     

    ----------

     

    Okay, and I can't even submit a post in Firefox now -- it shows a red "Please write something in the comment box." message that's clearly related to the error that has plagued me for years on Curse sites in various browsers. For a while I could only post on Curse.com by using Internet Explorer. Then it started to work in Opera, but IE and Firefox didn't work; apparently that's still the case. I've submitted multiple reports about this for years, but apparently nobody cares, since the only reply I've ever gotten is "ummm try a different browser?" and it's never been fixed.

     

    ----------

     

    Nope, can't post from Opera either... when I click "post reply" it grays out the box for a few seconds and looks like it's doing anything, but then becomes interactable again and nothing actually happens. Let's try IE!

     

    Success in IE. How is it so hard for you guys to make a website that just works in all standards-compliant web browsers? It's not 1996 anymore. We don't do the whole "this site requires Netscape Navigator at 800x600 screen resolution" crap anymore, guys. -_-

     

    ----------

     

    Edit #2 -- Also, seriously, please stop with the "are you sure you want to leave this page" javascript popup when I try to close the browser window. THAT is obnoxious.

    Posted in: WoW Sites Feedback
  • To post a comment, please or register a new account.