compose screen: email body should have role textbox



Firefox OS
3 years ago
3 years ago


(Reporter: MarcoZ, Unassigned)


(Blocks: 1 bug, {access})

Firefox Tracking Flags

(Not tracked)


(Whiteboard: [b2ga11y p=1])


(1 attachment, 1 obsolete attachment)

46 bytes, text/x-github-pull-request
: review+
Details | Review | Splinter Review


3 years ago
Otherwise the screen reader won't know what type of control that is.

Comment 1

3 years ago
Created attachment 8529204 [details] [review]
add role textbox
Attachment #8529204 - Flags: review?(jrburke)

Did you test this?
It also most likely need aria-multiline set to true.
Comment on attachment 8529204 [details] [review]
add role textbox

:yzen's comment around multiline seems relevant. Can you add that, then rebase/squash the pull request so that there is only one commit in the pull request, then flip review back to me.
Attachment #8529204 - Flags: review?(jrburke)

Comment 5

3 years ago
I've done the fix but didn't see how to merge the two commits in the PR (still not very familiar with github)

Comment 6

3 years ago
Comment on attachment 8529204 [details] [review]
add role textbox
Attachment #8529204 - Flags: review?(jrburke)

Comment 7

3 years ago
done but this time it merge my fix with another one I'm working on sorry for that I hope it will be ok

Comment 8

3 years ago
Comment on attachment 8529204 [details] [review]
add role textbox
(In reply to aurelien levy from comment #7)
> done but this time it merge my fix with another one I'm working on sorry for
> that I hope it will be ok

Hi Aurelien, this is great! We would however need to have a clean pull request in order to be able to include it into master. I would suggest using git cherry-pick to selectively apply only the necessary commit in your branch for this bug. Then you should be able to use git push -f to update the branch/pull request without closing it.

Comment 10

3 years ago
Comment on attachment 8529204 [details] [review]
add role textbox

Comment 11

3 years ago
ok this time it must be good I hope
Comment on attachment 8529204 [details] [review]
add role textbox

This is looking good, but just stuck on some of the mechanics around git. There is definitely a learning curve with git and GitHub, so this is to be expected. Since git is very flexible, this means that there are normally multiple ways to accomplish a task, making it more confusing. Thanks for sticking with it! 

Here is what I suggest to get the change in a format that we expect. This is generally the workflow I use whenever doing a new change. I apologize if this repeats things you already know, just listing it all for completeness.

From your fork of gaia, the one you have at, clone that locally, and set up a "remote" that is called "upstream" that points to the mozilla-b2g/gaia repo:

  git clone --recursive gaia-goetsu
  cd gaia-goetsu
  git remote add upstream

For each bug you are working on, create a branch to work on it. This branch will be used for the pull request when you are ready. So taking this bug as an example, and assuming you are starting in your clone's `master` branch in the `gaia-goetsu` directory:

  # this updates your local master to match mozilla-b2g's latest master
  # you should always do this to give better odds your change will work
  # with the lastest master state for when the pull request is merged
  git pull upstream master

  # this updates your fork on github's master to match
  git push origin master
  # Create bug-specific branch based on current state of master
  git checkout -b bug1068713-email-compose-role master

Now you will be in the `bug1068713-email-compose-role` branch locally, and its contents will look the same as the `master` branch. The idea with bug-specific branches is that you keep your master branch pristine and only matching what is in the official mozilla-b2g branch. No other local changes. This can be useful for comparisons or rebasing.

Do the changes to apps/email/js/cards/compose.html. As a review note, we are trying to get to a place with our HTML such that no line goes over 80 characters, and this change would push that div over 80. So we just break somewhere in the attribute list. Example:

  <div data-prop="textBodyNode" class="cmp-body-text" 
       contenteditable="true" role="textbox" aria-multiline="true"></div>

Commit the change to the branch and then push the branch to your fork. For the commit message, you can just copy in the title of the bug:

  git commit -am "Bug 1068713 - compose screen: email body should have role textbox"
  git push origin bug1068713-email-compose-role

Now you can go to and do the pull request.

In the course of the review, if you need to do other commits to the branch for review feedback, once it is all reviewed, you can flatten all the commits into one commit, then force push the change to your branch. I normally use `rebase -i` for this. So, in the `gaia-goetsu` directory, while you are in the `bug1068713-email-compose-role`, you can run:

  git rebase -i upstream/master

At this point, git gives you a way to edit all the commits. I normally 'pick' the first one, then choose 's' for squash for the rest, so the rest of the commits are squashed to the first picked commit.

Once that is done and git is happy, you can the force push the new state of the branch back to GitHub:

  git push -f origin bug1068713-email-compose-role


Once you update this bug with a pull request that gives a result like the above, flip the review back to me, and then it should be easy to r+ it and land.
Attachment #8529204 - Flags: review?(jrburke)

Comment 13

3 years ago
this close to what I have done until the rebase part this is what is missing with the last one ?
There are two commits in the pull request and from "unknown repository". It should just be one commit, and ideally from a branch/location that github could figure out. I am looking at:

which is the attachment that was marked for review. It looks like you also left a comment about this pull request:

That one has 5 commits in it, where ideally there should only be one. It might be good to just start with a fresh branch and do the change (the branch can have any name you like, just helpful if it has bug number in it somewhere).

Then, for whatever pull request you want reviewed, create a new attachment for it. There should be an option (may be hidden at first) when creating the new attachment where you can state that it makes the other attachment "obsolete".

Comment 15

3 years ago
yes that the case the only PR to consider is

So if I understand I need to restart from scratch again to just have one commit in the PR ?
- remove my distant copy on
- remove my local copy, 
- refork online, 
clone it locally, 
- make the branch locally, 
- make the changes locally, 
- commit the changes to the branch locally, 
- push the branch to online fork, 
- make the PR online
Once again sorry about that but I choose the hard way to learn git I suppose ;)


3 years ago
Attachment #8529204 - Attachment is obsolete: true
Your fork of is fine, unless you modified your master to be different from mozilla-b2g's master. If that is the case, you can remove your distant copy and starting over as you listed.

We have all had some weird problems with git while learning it and a particular project's process around using it. I still mess up from time to time. The nice thing is that most of it is recoverable by resetting in some way.

Comment 17

3 years ago
Created attachment 8529948 [details] [review]
Bug 1068713 - email body role textbox

This time I think it's the good one
Attachment #8529948 - Flags: review?(jrburke)
Comment on attachment 8529948 [details] [review]
Bug 1068713 - email body role textbox

Merged in master:

from pull request:

Congratulations, and thank you!

For future pull requests, when modifying the HTML, we are trying to move to a "max 80 characters per line" for them. We do not quite have that yet due to some legacy stuff, but want to do that going forward.
Attachment #8529948 - Flags: review?(jrburke) → review+


3 years ago
Last Resolved: 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.