Opened 9 months ago

Closed 8 months ago

#6003 closed change (fixed)

Better handling of no-content-for-platform-message on help.eyeo.com

Reported by: ire Assignee: ire
Priority: P3 Milestone: help.eyeo.com 1.0.0
Module: Websites Keywords:
Cc: jeen, juliandoucette, wspee Blocked By:
Blocking: Platform: Unknown / Cross platform
Ready: yes Confidential: no
Tester: Unknown Verified working: no
Review URL(s):

https://codereview.adblockplus.org/29607560/

Description (last modified by lisabielik)

Background

In #5912 we showed or hid certain aspects of the article content depending on the browser selected. If there is no content for the browser selected, we showed the following message at the beginning of the article:

Unfortunately, there is no content specific for your current browser. Please use the dropdown menu above to choose a different browser.

(See attachment for how it currently looks)

What to change

Update the message to the following:

Oops! There is no article for the subject and browser that you have selected. Please find a list of browsers that this article is available for below.

Below this message, provide a list of browsers that the current article does support.

  • {Platform 1}
  • {Platform 2}
  • {Platform 3}

When the user clicks on a platform, the appropriate content should be displayed.

Attachments (1)

Screen Shot 2017-11-08 at 8.50.29 am.png (93.7 KB) - added by ire 9 months ago.

Download all attachments as: .zip

Change History (13)

comment:1 Changed 9 months ago by ire

  • Description modified (diff)

comment:2 Changed 9 months ago by jeen

Update the text and add links to supported browser articles:

Unfortunately, there is no content specific to your current browser. Please choose a different browser from the list below:`

  • {Platform 1}(link to article)
  • {Platform 2}(link to article)
  • {Platform 3}(link to article)

This would make the text appear more prominant and mean the styling suggestion is no longer required.

comment:3 follow-up: Changed 9 months ago by ire

@Jeen: Thanks! I agree with you that the current solution is not ideal because the browser dropdown currently contains all the supported browsers, whether or not there are articles for that browser or not.

My main issue with your suggested method is that the list of browsers is like a duplication of the browser selector. (Plus, they won’t be links, they will be buttons because there aren't separate article pages for each browser).

My suggestion:

If the user visits the page in, for example Microsoft Edge, and there are no articles for that browser, the message should show:

Unfortunately, there is no content specific for your current browser. 
Please use the dropdown menu above to choose a different browser.

Then, in the browser dropdown, we will disable/hide all options that aren’t available for the current article.

What do you think?

comment:4 Changed 9 months ago by ire

  • Description modified (diff)
  • Ready set

comment:5 in reply to: ↑ 3 Changed 9 months ago by ire

Replying to ire:

@Jeen: Thanks! I agree with you that the current solution is not ideal because the browser dropdown currently contains all the supported browsers, whether or not there are articles for that browser or not.

My main issue with your suggested method is that the list of browsers is like a duplication of the browser selector. (Plus, they won’t be links, they will be buttons because there aren't separate article pages for each browser).

My suggestion:

If the user visits the page in, for example Microsoft Edge, and there are no articles for that browser, the message should show:

Unfortunately, there is no content specific for your current browser. 
Please use the dropdown menu above to choose a different browser.

Then, in the browser dropdown, we will disable/hide all options that aren’t available for the current article.

What do you think?

Jeen and I had a meeting and decided to go with her method.

comment:6 Changed 9 months ago by ire

  • Owner set to ire
  • Summary changed from Better styling for no-content-for-platform-message on help.eyeo.com to Better handling of no-content-for-platform-message on help.eyeo.com

comment:7 Changed 9 months ago by ire

  • Review URL(s) modified (diff)
  • Status changed from new to reviewing

comment:8 Changed 9 months ago by ire

During review, Julian raised some concerns about the message being shown.

On 2017/11/15 18:03:33, juliandoucette wrote:

"Your current browser" means "the browser that you are using" AFAICT. Which
doesn't make sense (is incorrect) if the selected browser is not the browser
that you are using.

Furthermore, this statement is ambiguous because "content" is general and is not
related to the subject/question in this statement. e.g. "there is no content
specific to your context" vs "there is no *answer* to *your question* in/for
*your context*" ... if you know what I mean?

I agree that the current message is flawed in the ways Julian mentioned

I also asked for some suggestions on what should replace the current message.

On 2017/11/15 18:03:33, juliandoucette wrote:

I hate writing... D:

I can suggest several elements:

  1. Oops sorry
  2. We don't have (an answer | a tutorial) (to $THIS_QUESTION | for

$THIS_SUBJECT) for $THIS_BROWSER

  1. Point to browsers that we do have (an answer | a tutorial) for
  2. Point at Popular Topics section (may not be necessary)
  3. Point at Still looking for help section (may not be necessary)

"Oops! There is no tutorial for the subject and browser that you have selected.
Please find a list of browsers that this tutorial is available for below. "

I like this suggestion.

@Jeen what do you think?

comment:9 Changed 8 months ago by lisabielik

Final wording agreed upon by all:

Oops! There is no article for the subject and browser that you have selected. Please find a list of browsers that this article is available for below.

comment:10 Changed 8 months ago by lisabielik

  • Description modified (diff)

comment:12 Changed 8 months ago by ire

  • Resolution set to fixed
  • Status changed from reviewing to closed
Note: See TracTickets for help on using tickets.